[dev] [commits] Horde branch master updated. 4fd2c31bf65accb6717f1330cbd8cc2b3ef1c9ba

[Michael J Rubinsky]

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> What I still really don't like is getting rid of CHANGES entries in  
>> our git tree until after a release. I still say it is useful for  
>> seeing what framework packages have changed since the last release.  
>> Unless the component script can give us an easy way to output those  
>> changes, *before* the release process, I'd like to see us keep  
>> them. Keep them off the website if you like, but I'd like to keep  
>> them in our tree.
>
> How is this any different than looking at the package.xml file?

Because I don't want to have to look at the package.xml file for every  
framework package to see which one has changes. The way it is now,  
with the framework changes in horde/docs/CHANGES it's very easy to see  
which package has had changes since the last Horde release. The Horde  
package.xml file did not contain these changes.

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org