On Thu, Nov 8, 2012 at 9:46 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Thu, 2012-11-08 at 07:33 -0500, Gary Gregory wrote: > > In Commons land we generate release notes automatically. Is there a > > reason it is not done this like here? > > > > Gary > > > > Gary > > No reason other than inertia on my part. I generally find it more > manageable updating the release notes at the same time as committing a > fix or a changeset to the repository rather than trying to generate > release notes shortly before a release. Usually, come release, I can > hardly remembering what all those issues were about. This also allows me > to omit issues I deem unimportant. But as any manual process, I fully > admit it can be error-prone. > It's the same process over there except that commits are made to code and to a changes.xml file which is used to generate an HTML report (as part of the Maven reports, see Commons IO [1] for example) and a txt file at release time. > I'll happily vacate the role of the release manager, though. > I think you are the best one for this project ATM. As for me, I do not know its innards well enough yet ;) Gary [1] https://commons.apache.org/io/changes-report.html > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
