> My personal feeling about this as a Jakarta (but not Tomcat) Committer
> is that the requirement for three binding (+1) votes before a public
> release is there to address the support issues. A (+1) vote on a public
> release should mean that you are signing-on for future development and
> support. In this particular context, Costin himself might only vote
> (+0) -- if he plans to only remain active outside Jakarta (developing
> facades and what-not). So at least three * other * Committers would
> need to sign-on with a (+1) before it "shipped".
I must clarify my understanding of the voting process ( or at least what
Brian and Roy described ):
1. The release proposal ( not the plan ) needs majority aproval, with
at least 3 "commited" +1s.
2. It seems he made a distinction between +1 ( I support the plan or
release ) and "commited" +1 ( I support the plan _and_ I commit to help).
3. My vote will be a "commited" +1.
I'm not sure what was the rule for a "release plan", but I suppose the
rules should be identical as for the final "release proposal".
In addition, I don't think a +1 vote on the release plan implys a +1 vote
on the final release - the plan is just a plan, and the "release
proposal" vote will be based on the plan execution.
I wouldn't mind to use the name "proposed 3.3" during plan execution,
meaning that the final name "3.3" will be used only after the _release_
itself is voted.
( I'll incorporate all the feedback I got during evening time, the lunch
brake is too short for that :-)
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
