Re: maintainer scripts

[John Stowers <john stowers lists gmail com>]

On Sun, 2008-07-27 at 01:50 +0200, daniel g. siegel wrote:
> On So, 2008-07-27 at 11:46 +1200, John Stowers wrote:
> > On Sun, 2008-07-27 at 01:08 +0200, daniel g. siegel wrote:
> > > another quick question: maintainer.py seems to pick up all bug fixes,
> > > but what about features, or other enhancements, which are no bugs? how
> > > do i get those into the NEWS file?
> > 
> > Check out 
> > http://svn.gnome.org/viewvc/conduit/trunk/NEWS?view=markup 
> > and
> > http://www.conduit-project.org/wiki/MakingARelease
> > 
> > If I make a commit, that adds a feature, not related to a bug # I add it
> > to NEWS directly. When maintainer.py makes the NEWS file any things I
> > had added to the current version section of the file get prepended to
> > the top of NEWS.new
> 
> i see. but wouldnt it be better then, to analyze the svn log until the
> last release?

Maybe, but I don't think so.

How would one determine which commits add features - perhaps a special
stanza in the message, e.g. #feature. What about new features that span
multiple commits, or if you forget to mention the new feature in the
commit message. 

I tend to make commit messages developer focused, i.e. "add foo_bar
function", not user focused.

John

> 
> daniel
> 
> > 
> > John
> > 
> > > 
> > > daniel
> > > 
> > > On Mi, 2008-07-23 at 18:17 -0400, Claudio Saavedra wrote:
> > > > El mié, 23-07-2008 a las 23:35 +0200, daniel g. siegel escribió:
> > > > > i just found some scripts like maintainer.py, list-translator.sh and
> > > > > so
> > > > > on.. does anybody use them for rolling your own tarballs? 
> > > > 
> > > > We use maintainer.py to prepare most of the stuff that should go into
> > > > NEWS before rolling tarballs. It makes it way easier!
> > > > 
> > > > Claudio
> > > > 
> > > _______________________________________________
> > > desktop-devel-list mailing list
> > > desktop-devel-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/desktop-devel-list
> >