Re: Stable branch release manager for Guile

[Rob Browning]

Marius Vollmer <address@hidden> writes:

> I added you to the list of Guile developers.  That means that you
> have write permission to CVS.  You should add your SSH key using
> "Account Maintainance", if you haven't done so already.

OK, I'm all set up now wrt CVS, so how do you (all) want me to handle
the stable release process?  How agressive should I be?  Do I need to
go through some formal process whenever I'm going to release? (I'm
mostly asking about consultations rather than just the steps that have
to be taken to make sure that the resulting tarball and CVS tags will
be right.)

Right now, there are some fixes that I already know should go into a
1.4.2.  There are two patches that have been sent to me by Marius (I
think) for inclusion in Debian's 1.4 that should more properly go into
a 1.4.2, and there are also the nasty sign extension bugs from a month
or so ago that should probably go in too.  Further, if the the CVS
guile-docs have made it in to unstable guile-core CVS, it might be
worth adding those to the stable branch too (once we have a stable
branch :>).

To some extent I'm also concerned about the mechanics, how I should
handle a patch that should go into a stable release *and* into the
unstable branch when it's not already there.  Should I submit it to
bug-guile, commit it to CVS myself, or what?

Thanks

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930