subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julianf...@apache.org
Subject svn commit: r1837961 - /subversion/site/staging/roadmap.html
Date Mon, 13 Aug 2018 16:02:30 GMT
Author: julianfoad
Date: Mon Aug 13 16:02:30 2018
New Revision: 1837961

URL: http://svn.apache.org/viewvc?rev=1837961&view=rev
Log:
* staging/roadmap.html
  (release-planning): Incorporate the major/minor/patch paragraph into this
    section, and remove the rest of the 'Previous Description'.

Modified:
    subversion/site/staging/roadmap.html

Modified: subversion/site/staging/roadmap.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/roadmap.html?rev=1837961&r1=1837960&r2=1837961&view=diff
==============================================================================
--- subversion/site/staging/roadmap.html (original)
+++ subversion/site/staging/roadmap.html Mon Aug 13 16:02:30 2018
@@ -143,27 +143,6 @@
 priority issues such as security and data loss or corruption. We may also
 sometimes fix other issues as appropriate to the emphasis of each release.</p>
 
-<h3>Transition to LTS and Regular Releases</h3>
-
-<p>Subversion 1.0 through 1.10 were released at intervals varying from around 6 months
in early versions to 2.5 years more recently. Each of those releases was supported with general
backports until the next release and with high priority fixes until the next release after
that.</p>
-
-<p>The LTS support schedule will apply also to 1.10 and 1.9 (the existing supported
releases), so each will receive support for 4 years from its initial release. General enhancements
will go into the regular releases and will not be backported to 1.10.</p>
-
-<h4>Previous Description</h4>
-
-<p>Subversion uses a compromise between time-driven and feature-driven
-release planning.  We schedule the next release for an approximate
-date (very approximate), and make sure it contains one or more new
-features or other significant differentiators, but we don't say
-exactly what those new features will be.  This is because we're always
-working on several things at once, and we want to give each new
-feature time to mature.  Especially given the decentralized nature of
-open-source development, we're wary of forcing technical discussions
-to premature consensus.  At the same time, it's good for the project
-to have regular releases, so we try to keep to a schedule and to
-have <em>something</em> ready to roll out when the release date comes
-along.</p>
-
 <p>In this context, "release" means an increment of the minor release
 number, which is the middle number in our three-component system.
 Thus, 1.2.0, 1.3.0, and 1.4.0 are successive minor releases in the
@@ -172,13 +151,20 @@ Thus, 1.2.0, 1.3.0, and 1.4.0 are succes
 releases far in advance, we just put them out when we feel enough
 bugfixes have accumulated to warrant it.  Major new releases, such as
 Subversion 2.0, will probably be done much like the minor releases,
-just with more planning around the exact features.  For more
-information about Subversion's release numbering and compatibility
-policies, see the section entitled
+just with more planning around the exact features.<p>
+
+<p>For more information about Subversion's release numbering and
+compatibility policies, see the section entitled
 <a href="/docs/community-guide/releasing.html#release-numbering" >"Release
 numbering, compatibility, and deprecation"</a> in the
 <a href="/docs/community-guide/">Subversion Community Guide</a>.</p>
 
+<h3>Transition to LTS and Regular Releases</h3>
+
+<p>Subversion 1.0 through 1.10 were released at intervals varying from around 6 months
in early versions to 2.5 years more recently. Each of those releases was supported with general
backports until the next release and with high priority fixes until the next release after
that.</p>
+
+<p>The LTS support schedule will apply also to 1.10 and 1.9 (the existing supported
releases), so each will receive support for 4 years from its initial release. General enhancements
will go into the regular releases and will not be backported to 1.10.</p>
+
 </div>
 
 <div class="h2" id="features-most-wanted">



Mime
View raw message