> 2) once all contributions have landed, cut the release branch; switch > all Jenkins jobs and Mustella runs to 'release'; leave the release > branch alone for 2 days so Mustella can be run in all configs. Wouldn't it be better if we didn't have to manually switch all of the Jenkins jobs? And then switch them back again after the vote? Less steps the better, we have already over complicated things. eg what use is trunk currently other than to cause the release manger merge issues? It is even tested? Are we 100% confident if we checked out of trunk we get the last released working version as opposed to the tagged release? (As aside I know but we keep seem to be adding more process not less is the point I'm trying to make).
I've got a VM that can still be setup to run run CI for the RCs if you need. > 3) if and when the all lights are green (no failing tests, all builds > correct), cut RC 1 and start the VOTE, preferably around a Wednesday - > that way there are a couple of work days and a weekend ahead, which > would allow both the worktimers and the weekenders to participate Seems reasonable and in perhaps means more involvement but it does prolong each release cycle by around 4 days to a minimum of a week and that's my concern. >From what I understand, it would be more time for 1 RC but less RCs and let the people with more time to test, not a good trade off ? -Fred
