jean-frederic clere wrote:
Bill Barker wrote:
I'm so tired of this thread, so let's settle it once and for all. I'm
backing Remy's suggestion to send the current trunk to the sandbox:
[X] +1 Let's end the revolution
I would also propose that we take an handling of releases similar to httpd.
See http://svn.apache.org/repos/asf/httpd/httpd/
branches contains the productions branches and the experimental
developpemnt branches.
trunk contains the place where the commmun developement and the new
agreed features and bugs fixes are going.
To move something from the "experimental developpement branches" to
trunk (or to a production branche) we vote it. (in a file named STATUS)
once accepted (no -1) the stuff enters the production or trunk. If
someone starts something in trunk and gets a -1 he should create a new
branche with the new code and propose a vote to get it back in trunk.
What does that means.
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/ will be moved to
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/branches/comet_dev (or
filip_dev)
A new http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/ (or better
http://svn.apache.org/repos/asf/tomcat/trunk/) will be created there we
put what we agree to put for the actual trunk (by voting).
Everyone that when to try something could try it in a new branche.
Comments?
Since the community is a bit small, it could be useful to precise that a
single +1 (from the committer who proposes the commit) is enough for a
commit to go through, rather than the usual 3 +1s.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
