I see no value to RCs around here. To me, RC's are valuable when the packaging is unstable, and you want a way for people to kick the tires of 'the package'. Our packaging is stable.
Any member of the community, even I, can check out the trunk and build the core and try it out. I don't need to wait for an RC for that. I'm in favor of just making releases and communicating to the user community what's in them. We could go as far as the HTTPD community and use a numbering convention for things that might not be suitable for the faint of heart. On Sun, Nov 25, 2012 at 3:17 PM, Mirko Friedenhagen <mfriedenha...@gmail.com> wrote: > Hello, > > I would support Stephen's suggestion and go with a quick 3.1.0 and > liked it better to fix-forward and release a 3.1.1 quite soon > afterwards. In the end you will get more feedback from a release then > from a RC. > > Regards Mirko > > On Sun, Nov 25, 2012 at 8:50 PM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: >> If you are going to help do another release in the next 2 months or so >> (barring unforeseen circumstances) my vote is Jenkins tip style, no RCs, >> early and often. >> >> If we are going to resume the snails pace (I hope not) then RCs >> >> Thst's my €0.02 >> >> -Stephen >> >> On Sunday, 25 November 2012, Jason van Zyl wrote: >> >>> I wish RCs were useful, but I don't believe anyone really looks or takes >>> the time to even try anything until it's actually released. >>> >>> It's not hard to make RCs. So if folks want them, not a problem, I can >>> roll an RC. >>> >>> Anyone have an opinion? >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder & CTO, Sonatype >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> --------------------------------------------------------- >>> >>> To do two things at once is to do neither. >>> >>> -- Publilius Syrus, Roman slave, first century B.C. >>> >>> >>> >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
