Submitted for your consideration.

  Please consider the question of a new versioning schema, based on
  Rich Bowen's interest in getting the website docs back to a reliable
  state, and reflecting the released versions of Apache.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97321 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 33 insertions, 1 deletions

diff --git a/STATUS b/STATUS
index 67a9b939e5..7b735662c0 100644
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/10/22 17:01:44 $]
+Last modified at [$Date: 2002/10/28 04:35:47 $]
 
 Release:
 
@@ -64,6 +64,38 @@ RELEASE SHOWSTOPPERS:
 
 CURRENT VOTES:
 
+    * Adopt backwards compatibility for future Apache 2.0 releases
+      such that MMN changes and eliminating non-experimental modules 
+      are deferred for the next minor version bump (e.g. 2.1, 2.2 
+      or 3.0).
+        +1: wrowe
+         0: 
+        -1: 
+
+    * Defer the Auth module overhaul to the next minor version bump
+      (e.g. 2.1, 2.2, 3.0) on the condition that forward compatibility
+      resolution is adopted.
+        +1: wrowe
+         0: 
+        -1: 
+
+    * Adopt an even/odd release paradigm (see VERSIONING) such that
+      even numbered releases are stable, and odd numbered releases 
+      are development efforts, keeping in the tradition of Linux, 
+      Perl, etc.  In pratical terms, this implies C-T-R-T-C, where
+      patches are (generally) first applied to the development branch,
+      tested, and then (after vote) applied to the stable branch.
+        +1: wrowe
+         0: 
+        -1: 
+
+    * Branch APACHE_2_0_BRANCH today, changing the version in CVS HEAD
+      to 2.1.0-dev.
+        +1 [from APACHE_2_0_43]: wrowe
+        +1 [from HEAD]: 
+         0: 
+        -1: 
+
     * httpd-std.conf and friends
 
       a) httpd-std.conf should be tailored by install (from src or