Sounds OK to me - the voting on plans seems to have been a recent addition.
I have something almost ready for Bug  38749 - which is in extras. I guess
from this, thats not affected as this is action only?

http://issues.apache.org/bugzilla/show_bug.cgi?id=38749

Niall

----- Original Message ----- 
From: "Wendy Smoak" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Monday, March 06, 2006 9:28 PM
Subject: Bylaws and Releases


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.

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.

Am I interpreting the bylaws correctly?  Is there an unwritten rule
about when you should call a vote on a release plan?

[1] http://struts.apache.org/bylaws.html

Thanks,
--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to