[dev] [commits] Horde branch master updated. 9dc818eece36dc23144c443a6b519f818cf75bde

[Jan Schneider]

Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> commit 1cdfb1a30fe7a1343f5350e932e5bb1d88edc0fb
>> Author: Jan Schneider <jan at horde.org>
>> Date:   Fri Apr 29 22:22:44 2011 +0200
>>
>>    BFN in horde's CHANGES too.
>>
>> framework/SyncMl/package.xml |    2 +-
>> horde/docs/CHANGES           |    1 +
>> 2 files changed, 2 insertions(+), 1 deletions(-)
>>
>> http://git.horde.org/horde-git/-/commit/1cdfb1a30fe7a1343f5350e932e5bb1d88edc0fb
>
> This is not correct.  We can't add changelog entries in horde (or  
> any other application) for *anything* that happens exclusively in  
> the packages; upgrading horde fixes nothing in this particular case.

My approach is this: package.xml files contain all the detailed  
changelogs for individual packages, mostly targeted for package  
consumers, i.e. developers that use our components.

But horde/docs/CHANGES is the only place visible in release  
announcements. So it's important to track bug fixes and new features  
there too. Of course not as much as in the package changelogs. Even if  
those changes are technically not in horde, and we can't even be sure  
that users will update framework packages too when updating horde. But  
it's the place where we traditionally keep log of framework changes.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/