Author: danielsh
Date: Fri Feb 27 17:55:10 2015
New Revision: 1662768
URL: http://svn.apache.org/r1662768
Log:
Explicitly document two-digit version number components.
* docs/community-guide/releasing.part.html
(#release-numbering): Document two-digit version number components.
* publish/docs/release-notes/1.9.html
(#next-release-is-1.10): New section.
Modified:
subversion/site/publish/docs/community-guide/releasing.part.html
subversion/site/publish/docs/release-notes/1.9.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=1662768&r1=1662767&r2=1662768&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Feb 27
17:55:10 2015
@@ -63,6 +63,10 @@ because eventually we declare a patch li
upgrade to the next minor release, so over the long run the numbering
is basically linear.</p>
+<p>The numbers may have multiple digits. For example, 1.7.19 is the nineteenth
+patch release in the 1.7.x line; it was released three years after 1.7.2, and
+three months before 1.7.20.</p>
+
<p>Subversion releases may be qualified by text following the
version number, which all represent various steps in the pre-release process.
In order from least- to most-stable:</p>
Modified: subversion/site/publish/docs/release-notes/1.9.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1662768&r1=1662767&r2=1662768&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Fri Feb 27 17:55:10 2015
@@ -100,7 +100,7 @@ and what impact these changes may have.<
<th>Minimum Repository</th>
<th>Notes</th></tr>
<tr>
- <td><a href="prospective-blame">Prospective blame</a></td>
+ <td><a href="#prospective-blame">Prospective blame</a></td>
<td>1.9</td>
<td>1.8</td>
<td>any</td>
@@ -213,6 +213,33 @@ example illustrates these changes.</p>
release might necessitate further adjustment by administrators or
users. We'll cover those in this section.</p>
+<div class="h4" id="next-release-is-1.10">
+<h4>Next release will be numbered 1.10
+ <a class="sectionlink" href="#next-release-is-1.10"
+ title="Link to this section">¶</a>
+</h4>
+
+<p>The next minor release after 1.9.0 will be numbered 1.10.0.</p>
+
+<p>Since "1.10.0" is smaller than "1.9.0" when considered as ASCII strings,
+scripts that compare Subversion versions as strings may fail to correctly
+determine which of "1.10.0" and "1.9.0" is the more recent one. Such
+scripts should be changed to compare Subversion version numbers correctly:
+as tuples of integers, with an optional suffix for development or pre-release
+versions. See
+<a href="/docs/community-guide/releasing#release-numbering"
+>the Subversion release numbering documentation</a>
+for details. (Programs written against the C API or the various bindings
+should refer to the
+<!-- TODO: link is broken (doxygen not yet generated) -->
+<a href="https://subversion.apache.org/docs/api/1.9/svn__version_8h.html";
+><tt>svn_version_*</tt> interfaces</a>.)</p>
+
+<p>The next patch releases on the 1.9.x line will be numbered 1.9.1, 1.9.2,
+…, as usual.</p>
+
+</div> <!-- next-release-is-1.10 -->
+
<div class="h4" id="auto-ignore-mishaps">
<h4>### Auto-ignore configuration mishaps
<a class="sectionlink" href="#auto-ignore-mishaps"
