Is there even a release manager concept though in that model? Anyone can
build candidate release artifacts and call for a vote? No that doesn't
make sense .. so we'd still need to have a vote to decide to do a release,
appoint a release manager and then that person calls for the vote on
actual candidate release artifacts. Is that the basic proposal?
Sanjiva.
Davanum Srinivas wrote:
new VOTE has to be explicitly started.
-- dims
On 5/2/07, Dinesh Premalal <[EMAIL PROTECTED]> wrote:
Hi,
"Davanum Srinivas" <[EMAIL PROTECTED]> writes:
> - All Release binaries must be be explicitly VOTE'd on
Just in case if release manager change release artifacts while VOTE
thread going on, Is it need to re-vote or Is it ok to go with old
votes? Anybody has an idea on this.
thanks,
Dinesh
--
Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
