natas_hw
/
ant-ivy
mirror of https://github.com/apache/ant-ivy
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Explain in more detail how we work with branches when creating a new release. 

git-svn-id: https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.4.0-rc1@1577374 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Maarten Coene 2014-03-13 23:23:48 +00:00
parent 1415de48df
commit 3378c9ab59
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/dev/makerelease.html
View File

@ -36,9 +36,12 @@ RELEASE_NOTES
CHANGES
README
<h3>2. Create a release branch</h3>
This will allow to work separately from other developers, in case you need any last modification.
This will allow to work separately from other developers, in case you need any last modification. For a release we have 2 branches. For instance, suppose we create a 2.0.0-beta1 release. We have a branch for the code for all 2.0.x releases, this is the '2.0.x' branch. From this branch we will create the release branch which is for a specific release. It is possible that the 2.0.x branch has already been created when releasing a previous version, in that case the creation of this branch can be skipped.
<code>
svn copy https://svn.apache.org/repos/asf/ant/ivy/core/trunk \
https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x \
-m "Creating a 2.0.x branch."
svn copy https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x \
https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1 \
-m "Creating a release branch for 2.0.0-beta1."
</code>