subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gst...@apache.org
Subject svn commit: r1298544 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Thu, 08 Mar 2012 20:00:34 GMT
Author: gstein
Date: Thu Mar  8 20:00:34 2012
New Revision: 1298544

URL: http://svn.apache.org/viewvc?rev=1298544&view=rev
Log:
Minor tweak to how we specify variable release versions.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1298544&r1=1298543&r2=1298544&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Thu Mar  8 20:00:34 2012
@@ -429,7 +429,7 @@ because its new name is fine.</p>
 
 <p>Minor and major number releases go through a stabilization period
 before release, and remain in maintenance (bugfix) mode after release.
-To start the release process, we create an "A.B.x" branch based on the
+To start the release process, we create an "<tt>A.B.x</tt>" branch based on the
 latest trunk, for example:</p>
 
 <pre>
@@ -1122,7 +1122,7 @@ A.B with the version you're preparing, e
 takes place there.  The only changes permitted are ones made to
 various bookkeeping files such as <tt>STATUS</tt>, and changes merged
 in from trunk.  In rare cases, a feature branch may be created from the
-A.B.X branch to address issues specific to the release branch (for example,
+A.B.x branch to address issues specific to the release branch (for example,
 to fix a bug that does not affect trunk).</p>
 
 <p>The protocol used to accept or refuse the merging of changes from



Mime
View raw message