I read the release process wiki page and at the risk of being flamed this seems a bit heavyweight, especially when releasing patch releases. I am not sure if I understand the need for voting and getting all the issues down to zero. Would it be possible to have different release requirements depending on the type of release (patch versus major)?
A committer fixes a couple of bugs and then: rake release - "Run specs, build gem, push to rubygems.com, done." It should be that simple. I am a big fan of buildr and I really want to see it thrive. I am willing to volunteer my time to help do whatever is needed to get buildr to that level of simplicity when releasing. Thanks, -russ On Mon, May 14, 2012 at 9:14 PM, Alex Boisvert <alex.boisv...@gmail.com>wrote: > On Mon, May 14, 2012 at 5:52 PM, Peter Donald <pe...@realityforge.org > >wrote: > > > My preference would be to aim for supporting/blessing > > * jruby-1.6.7 > > * ruby-1.9.2-p320 > > * ruby-1.8.7-p358 > > > > These would be my preferences too. > > alex >
