Hi Caleb, On Jun 8, 2012, at 12:00 PM, Caleb James DeLisle wrote:

After some discussion on IRC, the current plan for releasing 4.1-rc-1 and 4.1 has been determined to be unworkable. The specific part at issue is the calling of a VOTE to release what is currently in the staging repository and waiting 72 hours for it to be verified. While this provides the best quality assurance, each blocker means another failed vote and another 72 hours + the time to fix the issue and stage another release.

Proposal: Stage the release 2 days before the official release date allowing blockers to be found and fixed. Fix the issues and release the resulting build without any guaranteed testing window, hoping that the patches to the earlier issues didn't introduce any regressions.

I don't like it much but it seems that it sucks less than all of the alternatives so +0 for me.

Once more I'm not very fond of double-staging... However I'm ok but it needs an associated testing strategy as otherwise there's no point of doing staging. What does it change for Sorin and others? So far, Sorin was manually testing the RC1 (ie after the RC1 release). What would it change for Sorin? Since during this period we'll see a lot of devs doing last moment commits I doubt Sorin can retest every time there's a change (+ it won't be restaged immediately). Thanks -Vincent