On 12/20/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
On Dec 20, 2006, at 7:57 PM, Craig McClanahan wrote:
> In general, there's only one thing I'm surprised isn't here ... the > declaration that a vote to actually do a release is a majority > vote. That > might be implied by the general Apache policies, but I think it'd > be good to state that explicitly. I don't have a problem with stating it explicitly.
Wait, what "vote to actually do a release" ? At Struts the guidelines say you post a release plan and/or announce your intentions on [EMAIL PROTECTED] The only vote is on whether (and at what quality) to release the package. If we're going to have project-level bylaws [1] then we should add a section with the procedure for changing the bylaws. Or we could just have project and release guidelines as part of the project docs, under commit-then-review like everything else, which IMO better fits how things actually happen. We're governed by the ASF bylaws, but at the project level things are far more informal. I don't think I've seen two releases done exactly the same way since I've been here... [1] Noel thinks they aren't necessary (and we removed that part of the board resolution for Tiles): http://mail-archives.apache.org/mod_mbox/incubator-general/200611.mbox/[EMAIL PROTECTED] -- Wendy
