You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2012/11/08 15:46:53 UTC

Re: svn commit: r1406998

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.

I'll happily vacate the role of the release manager, though.

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Re: svn commit: r1406998

Posted by Oleg Kalnichevski <ol...@apache.org>.
On Thu, 2012-11-08 at 09:54 -0500, Gary Gregory wrote:
> 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 adjust if someone can lay the groundwork for using
changes.xml instead of a plain RELEASE_NOTES.txt.

Oleg



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Re: svn commit: r1406998

Posted by Gary Gregory <ga...@gmail.com>.
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-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@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