I agree with Stephen and Tony. If you think it still needs some time for testing, do yet another beta release. If you think it's ready and want to final tests, stage a 1.0 release and do the vote.
If some bugs show up after a 1.0 release (which it ALWAYS does), you just need to do a bugfix release. Standard procedure. I'm 0 on this vote. /Anders On Fri, Jan 13, 2012 at 09:30, Tony Chemit <[email protected]> wrote: > On Fri, 13 Jan 2012 08:22:33 +0000 > Stephen Connolly <[email protected]> wrote: > >> don't know when. >> >> personally, i see the point in alpha and beta... but for plugins, i >> think rc's *when there has been no full release* are just noise... >> users will generally not use them unless they were using the betas, >> and we risk burning ourselves out testing... >> >> i see a point in making an rc release if you have done a major >> refactoring on an already released plugin... and you want >> feedback.... but a beta would serve just as good. >> > +1 Why not just do a beta-2 release vote ? > > The only other project which has done it was > > selenium-maven-plugin-1.0-rc-1/ (out of more than 500 releases in > mojo :). > > Tony. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
