Why should you limit to just one volunteer? The idea is that the procedure in http://wiki.apache.org/cassandra/HowToPublishReleases should be followable by any Cassandra committer.
I would propose that the release manager is the person who steps up to run the release for that specific release. If it is just one person always making releases then that becomes a SPOF... better to have more than one and round-robin it, or have one do the stable releases and the other do the new releases... I'd volunteer as well only I don't have commit access... (I have access to publish to maven central on behalf of cassandra, but that's a whole other story) -Stephen On 13 April 2011 22:43, Sylvain Lebresne <sylv...@datastax.com> wrote: > That is probably a mistake I'm going to regret soon enough, but since > it doesn't sound > I'm stealing the idea to anyone I'm volunteering. > > -- > Sylvain > > On Mon, Apr 11, 2011 at 11:43 PM, Eric Evans <eev...@racklabs.com> wrote: >> On Mon, 2011-04-11 at 16:40 -0500, Eric Evans wrote: >>> The amount of time I'm able to commit to Cassandra going forward is >>> uncertain, plus, it wouldn't hurt give someone else a turn, or to have >>> some redundancy here. Do we have any volunteers? >>> >>> The requirements are: >>> * Committer >>> * Gluten for punishment >> >> That would be "glutton" of course, release management is 100% >> gluten-free. >> >> >> -- >> Eric Evans >> eev...@racklabs.com >> >> >
