You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2012/12/13 21:34:10 UTC
svn commit: r1421500 -
/isis/site/trunk/content/contributors/release-branch-and-tag-names.md
Author: danhaywood
Date: Thu Dec 13 20:34:10 2012
New Revision: 1421500
URL: http://svn.apache.org/viewvc?rev=1421500&view=rev
Log:
isis site : refining release process docs
Modified:
isis/site/trunk/content/contributors/release-branch-and-tag-names.md
Modified: isis/site/trunk/content/contributors/release-branch-and-tag-names.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/contributors/release-branch-and-tag-names.md?rev=1421500&r1=1421499&r2=1421500&view=diff
==============================================================================
--- isis/site/trunk/content/contributors/release-branch-and-tag-names.md (original)
+++ isis/site/trunk/content/contributors/release-branch-and-tag-names.md Thu Dec 13 20:34:10 2012
@@ -6,7 +6,7 @@ In Isis the version numbers of core and
(they are not synchronized); therefore the branches and the tag names must
distinguish the releasable module that they refer to.
-The following table summarizes the branch name to use for release preparation, and the tag name to use when the release is pushed for review.
+The following table suggests the branch name to use when readying the release locally, and the tag name to use when running the `release:prepare` command itself. If the release is voted through, this tag will be the permanent identifier of the release within the git source code repository.
<table>
<tr>