Mark Thomas wrote:
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
branch with the new code and propose a vote to get it back in trunk.
+1 to this combined approach. I like it.
Yes, maybe it can work due to the centralized file. A separate vote
thread for each commit would not work. This would need to be a separate
discussion and vote, though.
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/
We already have this and it is, as far as I am concerned, the current
trunk.
I like the idea of keeping each major release in a separate directory
under http://svn.apache.org/repos/asf/tomcat/. It keeps everything
nice and consistent (something I like). Therefore I am -0 on moving
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/* to
http://svn.apache.org/repos/asf/tomcat/
There's a 6.0.x trunk to which some patches can be merged, and I also
like the separate folder.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
