svn commit: r290162 - /httpd/httpd/trunk/VERSIONING

[co...@apache.org]

Author: colm
Date: Mon Sep 19 07:11:46 2005
New Revision: 290162

URL: http://svn.apache.org/viewcvs?rev=290162&view=rev
Log:

s/CVS/subversion/ : no policy changes.


Modified:
    httpd/httpd/trunk/VERSIONING   (contents, props changed)

Modified: httpd/httpd/trunk/VERSIONING
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/VERSIONING?rev=290162&r1=290161&r2=290162&view=diff
==============================================================================
--- httpd/httpd/trunk/VERSIONING (original)
+++ httpd/httpd/trunk/VERSIONING Mon Sep 19 07:11:46 2005
@@ -1,6 +1,6 @@
 APACHE 2.x VERSIONING
 =====================
-Last modified at [$Date$]
+[$LastChangedDate$]
 
 
 INTRODUCTION
@@ -67,11 +67,11 @@
     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.

Propchange: httpd/httpd/trunk/VERSIONING
------------------------------------------------------------------------------
    svn:LastChangedDate = on