Hi,
On Thu, Nov 29, 2012 at 5:42 PM, Simone Tripodi <[email protected]> wrote: > nice that you started the topic! MY personal opinion is that > changes.xml smells like something obsolete, since JIRA supports > release notes for each version, have a look for example at an old > fluido release[1]. > > So, I would be more to tracking release notes in a txt file rather > than in redundant changes.xml with info already contained in JIRA. I am fine with that. Just saw, it can generate Release Notes component wise. That might be enough. In addition, the mvn changes plugin can do something with JIRA. If we match version numbers of the pom.xml with the ones in Jira, we might have an easy game for... whatever. Cheers > > WDYT? > thanks and best, > -Simo > > [1] > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430&styleName=Html&version=18296 > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Thu, Nov 29, 2012 at 4:40 PM, Christian Grobmeier > <[email protected]> wrote: >> Folks, >> >> I just committed the log4j2 module to onami logging. >> >> That said, I didn't find a changes.xml file. >> >> Have we agreed on how we track our changes? >> >> Cheers >> Christian >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de
