Like Jan says, it'd be awesome to have more people familiar with the release procedure. Although if you're interested in speeding up releases the best place to start would be by learning some internals. The issues that usually keep things from shipping is that a test is randomly failing or there's a bug waiting to be fixed.
On Tue, May 10, 2011 at 3:34 AM, Jan Lehnardt <j...@apache.org> wrote: > Dirkjan, > > thanks for your offer, I think it is a great idea to add more helping > hands to the release process. > > The first stop for making a release is > http://wiki.apache.org/couchdb/Release_procedure > > In general, you should be able to build and test CouchDB from source > and be comfortable with the troubleshooting of issues, but I know > you are :) > > Cheers > Jan > -- > > > On 10 May 2011, at 09:25, Dirkjan Ochtman wrote: > >> Hi there, >> >> Since I note that the release process for 1.1 seems to have been >> stalled again, I wonder if there was stuff I could do. I'd be happy to >> join the RM team to help Apache CouchDB provide more timely releases >> so that companies like mine can benefit sooner from the latest fruits >> of the committers. >> >> Please let me know how I would go about learning all the stuff I need >> to know (and hopefully at some point keys to the required infra). >> >> Cheers, >> >> Dirkjan > >
