[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[PATCH] Wording on "Roadmap" web page

From: Peter Samuelson <peter_at_p12n.org>
Date: 2006-02-06 22:10:48 CET

[Julian Foad]
> "We schedule each release for a certain date, [...]"
>
> That's not very true, is it? Would someone like to replace that with
> something suitably vague

[[[
Clarify release schedule.

Patch by: Peter Samuelson <peter@p12n.org>

* www/roadmap.html (release-planning): Remove implication that release
  planning is particularly time-based.
]]]

Index: www/roadmap.html
===================================================================
--- www/roadmap.html (revisione 18242)
+++ www/roadmap.html (copia locale)
@@ -28,8 +28,7 @@
 <div class="h2" id="release-planning" title="release-planning">
 <h2>How We Plan Releases</h2>
 
-<p>Subversion uses a compromise between time-driven and feature-driven
-release planning. We schedule each release for a certain date, and
+<p>Subversion release planning is mainly feature-driven. We try to
 make sure a release 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
@@ -37,8 +36,8 @@
 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 <i>something</i> ready to
-roll out when the release date comes along.</p>
+so we try to have <i>something</i> ready to roll out every few months,
+on average.</p>
 
 <p>In this context, "release" means an increment of the minor release
 number, which is the middle number in our three-component system.

Received on Mon Feb 6 22:18:47 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.