summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorColm MacCarthaigh <colm@apache.org>2005-09-19 16:11:46 +0200
committerColm MacCarthaigh <colm@apache.org>2005-09-19 16:11:46 +0200
commitd73f1f37ae56df6fee52ecab060451f221e9dd8e (patch)
tree67e6206ec0f955871cabdbe972414fe4d451ddd1
parentBackported to the 2.1.8/2.2.x tree (diff)
downloadapache2-d73f1f37ae56df6fee52ecab060451f221e9dd8e.tar.xz
apache2-d73f1f37ae56df6fee52ecab060451f221e9dd8e.zip
s/CVS/subversion/ : no policy changes.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@290162 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to '')
-rw-r--r--VERSIONING10
1 files changed, 5 insertions, 5 deletions
diff --git a/VERSIONING b/VERSIONING
index 3bfea278b1..613f19ca7d 100644
--- a/VERSIONING
+++ b/VERSIONING
@@ -1,6 +1,6 @@
APACHE 2.x VERSIONING
=====================
-Last modified at [$Date$]
+[$LastChangedDate$]
INTRODUCTION
@@ -67,11 +67,11 @@ keeping the stable tree as safe as possible:
to the 2.4-stable release if they cannot be incorporated in the current
stable release due to API change requirements.
- * The stable CVS tree should not remain unstable at any time. Atomic commits
- aught be used to introduce code from the development version to the stable
- tree. At any given time a security release may be in preparation,
+ * The stable subversion tree should not remain unstable at any time. Atomic
+ commits aught be used to introduce code from the development version to the
+ stable tree. At any given time a security release may be in preparation,
unbeknownst to other contributors. At any given time, testers may be
- checking out CVS head to confirm that a bug has been corrected. And as
+ checking out SVN trunk to confirm that a bug has been corrected. And as
all code was well-tested in development prior to committing to the stable
tree, there is really no reason for this tree to be broken for more than
a few minutes during a lengthy commit.