Well the only issue I see is that you have to send the [ANN] mails and publish the site updates after the vote.... but you still have to wait for the sync to central before you can send those too... so that's a potential delay of 8hr anyway
My preference is that the criteria is "at least 3 * +1 from mojo developers OR 72h lazy consensus whichever comes first" I am open for bug fix only releases to shorten to 36 or 48h. For 0-day security fix releases I think we would need some policy or other (but given this is a build tool I don't see a major risk of these occurring) Once Ben gets the SCP site deploy code that I wrote in place, pushing plugins should be a lot quicker from the developer's time perspective... at the moment it takes me a couple of hours to push a plugin release over webdav due to some wagon issue that I have been unable to nail down with ben. -Stephen On 17 May 2012 15:07, Anders Hammar <[email protected]> wrote: > Not sure I understand your point. If you fix the bugs, stage the > release and start the vote on Sunday, you could promote the release > (if voting is in favor) at any point. You don't have to close the vote > after exactly 48 hours (for example). > > But I understand that it could mentally feel good to do everything and > get the release out in the same go. But the cost of (new) errors is to > high IMHO. > > /Anders > > On Thu, May 17, 2012 at 11:59 AM, Christopher Hunt > <[email protected]> wrote: >> One final view if I may (looks as though the vote is dead anyhow). :-) >> >> Like many here I'm sure, I have a full-time job. For me to get in there, fix >> a few bugs, release and then exit, not requiring a vote makes this >> practical. If you require voting of 24, 48 or 72 hours, then that is another >> day. May be I fix the bugs on Sunday. I'm at work on Monday and Tuesday. >> Opportunity gone. This is my reality. >> >> Enough said though. I must naturally go with the consensus. >> >> Thanks for the hearing. >> --------------------------------------------------------------------- >> 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
