> -----Original Message----- > From: Maczka Michal [mailto:[EMAIL PROTECTED] > Sent: jeudi 1 juillet 2004 09:52 > To: 'Maven Developers List' > Subject: RE: when to touch changes.xml/project.xml version RE: cvs commit: > maven-plugins/java project.xml > > > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Thursday, July 01, 2004 7:46 AM > > To: 'Maven Developers List' > > Subject: RE: when to touch changes.xml/project.xml version RE: cvs > > commit: maven-plugins/java project.xml > > > > > > Brett, > > > > Why not take the easy route, that is, if not already bumped > > then bump the > > plugin version for whatever change you're bringing. It just won't be > > released before there are any significant changes to it. > > > +1 > > Simple and clear rule. > > I would add that new entry in changes.xml file must be added to explain > what > already happen and why the version was bumped. > Even (I think it is not good idea) if somebody will find some information > in > this file irrelevant for > end users - they still can be removed during the release process.
I don't quite agree on this last point... :-) The point of the changes.xml file over the changelog report generation is precisely that we are filtering what is useful for end users to know. If a plugin developer want to know what was the reason for such and such modification, he can consult the CVS commit comments and diffs. -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
