Noel J. Bergman wrote:
Ok, 3 days passed.
Code changes can be vetoed at any time, resulting only in the inability to
cut a release containing them.
--- Noel
Sorry but I don't understand your sentence.
I just read again the http://www.apache.org/foundation/voting.html and
it seems that we followed the right procedure. That page does not say
anything about your sentence. I don't have anything with that "rule" but
you should add the rule to that page so anyone will know how VOTEs work.
> Votes should generally be permitted to run for at least 72 hours to
> provide an opportunity for all concerned persons to participate
> regardless of their geographic locations.
DONE
> Votes on Code Modification
> Unless a vote has been declared as using lazy consensus, three +1
> votes are required for a code-modification proposal to pass.
DONE
> Votes on Package Releases
> Votes on whether a package is ready to be released follow a format
> similar to majority approval -- except that the decision is
> officially determined solely by whether at least three +1 votes were
> registered. Releases may not be vetoed.
This one say something different (against) your sentence: in fact once
this vote has passed I understand that we could start a vote for a
release and vetoes would not be applicable.
Did I understand wrong? is the voting explanation page outdated? Can you
elaborate?
Thank you,
Stefano
PS: again, I don't have problem with "your rule", because I think we
should not need a strict rule for voting as they are a tool to express
opinions and opinions can change or anything else, but since your
sentence is not clear to me wrt "apache rules" I would like to understand.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
