Re: Why <changelog>?

Hi In my experience, it's enough if you just write the changes in the latest release. This is then added into the database. No need to keep all changes in the package.xml (but this is just my experience, not sure if this is intented behaviour...) chregu On Thu, 9 Jan 2003, Jon Parise wrote: > I've been maintaining a few PEAR packages for a while now (long enough > for each package to have accumulated a number of releases). One of > the most tedious (and, in my opinion, unnecessary) steps in releasing > a new version of a PEAR package is updating the <changelog> block to > contain the previous release's details. > > I'm now curious: > > Why must package maintainers track the set of changes in the > package.xml file? > > It seems like an data-based operation that _should_ be handled by the > scripts and database on pear.php.net (e.g. when a new release is > submitted, the changelog is updated). > > Can someone shed some light on why this isn't the way things are > currently done? > > -- nam...christian stocker adr...pflanzschulstr. 31, ch-8004 zurich pho...+41 43 317 9984 www...http://phant.ch/chregu mob...+41 76 561 8860 ema...chregu@phant.ch wor...+41 1 240 5670 gpg...0x5CE1DECB