On 3/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > Having volunteered as release manager Struts Action 1.3.1, I'm reading > the instructions. :) > > The bylaws [1] say that release plans must be announced on the dev > list and that each issue is decided by lazy majority.
Right. In the old days, the release plans were part of the site, generated from XML, so we needed to announce them so that people would know they were there. These days, we use the wiki for the release plans, so the announcement is not strictly necessary (since people see the wiki notification). Still, an announcement is not a bad idea. The individual issues are also tracked on the wiki as part of the release plan now, so it's much easier to keep track of current status. If someone doesn't like what they see on the wiki page, they'll usually post to the list about it. I think that fits as "lazy". ;-) I interpret this to mean that I can [ANNOUNCE] the release plan and > the intended date, then proceed with tagging the repository and > creating the test build, as long as -1's do not outnumber +1's. In > practice, of course, any -1 is likely to stop the process. > > But that's not what has happened for recent releases-- [VOTE]s have > been called to confirm the release plans themselves, and then again > for the quality of the proposed releases. As Niall pointed out, voting on the release plans themselves is a recent thing, but it's not necessary. For "big" changes, like the first 1.3 test build, it's not a bad idea, so that we're all sure we're on the same page, but in general, we've often said that anyone can produce a test build. Really, the worst that could happen is that it doesn't get a good quality vote. I'd suggest that you either 'announce' the release plan, to make sure everyone is on board, providing a link to the wiki page that includes all the relevant issues, or just send an 'STP' message (Short Term Plan) stating your intent to roll a test build. Am I interpreting the bylaws correctly? Is there an unwritten rule > about when you should call a vote on a release plan? No, I don't think there are unwritten rules. Our current system is effectively "build first, vote later", because we don't classify the test build as a release - it's just that, a Test Build. So, basically, go for it, Wendy. :-) And thanks! -- Martin Cooper [1] http://struts.apache.org/bylaws.html > > Thanks, > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
