On Fri, Mar 9, 2012 at 2:19 PM, Stefan Sperling <s...@elego.de> wrote: > On Fri, Mar 09, 2012 at 08:10:27PM +0200, Daniel Shahaf wrote: >> Stefan Sperling wrote on Fri, Mar 09, 2012 at 10:21:33 +0100: >> > Any volunteers? >> >> I'll consider throwing my hat in the ring, when the need for 1.7.5 comes >> around. > > Nice, thanks :) > >> Who's going to fulfill the "running" responsibilities of the RM? >> Updating CHANGES as backports get merged, calling "let's roll 1.7.(++x) >> next week", etc? > > Whoever declares himself RM for the current round, I guess. > > Someone (or something) needs to bootstrap the process by suggesting that > a new release should be made soon. We could share the responsibility of > reminding each other about it. Or we could have a bot that does this for us. > > E.g. we could define a schedule that says "a new patch release should > be issued at least every N weeks" at which point we'll get an automated > reminder sent to dev@ from some cronjob. Anyone would then be eligible to > grab the RM hat by replying to this notice.
Or even "looks like M things have been merged since the last release". -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
