I like the changes page as a "simplified, user-friendly" list of notable changes made for each release. The defect/RFE tracking system has the details for the initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>: > On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > > > I never really understood the changes.xml myself, as I don't want to > > keep things in an issue tracking system and changes.xml or is this > > for folks who don't employ an issue tracking system? > > Yes and no. I've always seen it as a "technical" changelog of the > project. When end-users create issues, the summary is not always > understandable so we end up with a list of "things" beings solved. > > The changes.xml allows to describe in more details what happened. It's > a good thing actually and it's certainly a good alternative for people > not using an Issue tracker that maven handles. > > Stéphane > > > > > > > - Keeping it in a maven-changes-plugin brings M1 and M2 more in > > > sync than they were before, which eases migration pains. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
