release-process.txt currently says:
>>>>
7. Check out DBCP fully - i.e., trunk, branches, tags.
8. From the top level of the checkout, execute
svn cp trunk branches/DBCP_1_3_x_BRANCH
svn commit -m "Created 1.3.x compatibility release branch."
(where x is the final digit of the new release number)
<<<<
This seems like a lot of SVN download traffic, and the amount will
increase with every new branch or tag added to DBCP.
Surely one can just create the tag directly in SVN, e.g.
svn copy -m"Create 1.3.x compatibility release branch." \
https://svn.apache.org/repos/asf/commons/proper/dbcp/trunk \
https://svn.apache.org/repos/asf/commons/proper/dbcp/branches/DBCP_1_3_x_BRANCH
The newly created branch can then be checked out locally.
Or am I missing something here?
We could create a script for creating the branch, and probably quite a
bit of the rest as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
