I think that all releases should require a vote to allow for people to verify and/or express an opinion on the release. The plugins here at Mojo are part of a project and shouldn't be seen as individual releases. Delaying a release slightly to ensure quality is a small price IMO.
That being said, I think that a shorter period of 48 hours (24h is too short I think) could be good enough for releases only including bug fixes (I like this definition better than "minor/micro release"). And that would then include a lazy consensus. I have no opinion against this being combined with something like 3x +1 (from mojo devs?), which ever comes first. /Anders On Thu, May 17, 2012 at 11:28 AM, Robert Scholte <[email protected]> wrote: > -1 on the 'Voting should not be a requirement for patch releases' > > We've seen already a lot of arguments. > I don't think that the 'time to vote' was the original problem, but the > content of the release (being only patches). > To vote should confirm that you didn't make any mistake, the project is > works on several platforms. It's so easy to introduce bugs, even with > patches. > > We can't know everything about all plugins and that is something we see > during votes of some projects. > For instance, I see a lot of work on the appassembler project, but I just > haven't got the time to dig into this project. A +1 vote for those releases > would add no value. > But what we could do is scan code, docs and sonar stats and base our vote on > that. > That would at least give the feeling you're not doing it only for yourself. > > Saying that, I tend to go for the "72h or 3x +1 (by mojo-devs?)" for > major and maybe "48h or 2x +1 (by mojo-devs?)" for minor > > -Robert >> Date: Thu, 17 May 2012 00:56:55 +0200 >> From: [email protected] >> CC: [email protected] >> Subject: Re: [mojo-dev] [VOTE] Voting should not be a requirement for >> patch releases > >> >> On Thu, 17 May 2012 00:47:11 +0200 >> Olivier Lamy <[email protected]> wrote: >> >> > +1 for patch release faster. (less than 72H : 24H or 48h. rm must be >> > able to have shorter time) >> > >> +1 for this idea, 72h is sometimes very long, ... when nobody else than >> yourself is voting to the release you are doing :( which is very common on >> the mojo project I think. >> >> >> >> -- >> Tony Chemit >> -------------------- >> tél: +33 (0) 2 40 50 29 28 >> email: [email protected] >> http://www.codelutin.com >> >> --------------------------------------------------------------------- >> 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
