Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 25 Nov 2009 20:31:20 -0000
Message-ID: <20091125203120.10287.1161@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSolr_Wiki=5D_Update_of_=22ReleaseVersioning=22_by_chrismattm?=
 =?utf-8?q?ann?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for chan=
ge notification.

The "ReleaseVersioning" page has been changed by chrismattmann.
The comment on this change is: skeleton release page: others, please add mo=
re!.
http://wiki.apache.org/solr/ReleaseVersioning?action=3Ddiff&rev1=3D1&rev2=
=3D2

--------------------------------------------------

- Describe ReleaseVersioning here.
+ =3D SOLR Release Versioning Scheme =3D
  =

+ There has been a lot of talk on the SOLR mailing lists (see http://markma=
il.org/message/o6b2lhuqpi4tefyo ) regarding the release version number sche=
me for Apache SOLR. We can use this Wiki page to collect thoughts on the su=
bject, and eventually (hopefully) document a simple, clear (and short!) pro=
cess here.
+ =

+ =3D=3D References =3D=3D
+ http://en.wikipedia.org/wiki/Software_versioning
+ =

+ =3D=3D Proposals =3D=3D
+ Here are some of the proposals put forth:
+ =

+  * [M.n] Chris Mattmann suggested the following scheme:
+      ''M.n''
+      =

+      Where ''M'' is the major version number. =

+ =

+      Where ''n'' is the minor version number.
+ =

+ In this type of scheme, all n's in a series are expected to be at least b=
ackwards compatible with n-1 through 0-9, but all M+1's aren't necessarily =
compatible with M or M-1.
+ =

+   * Some other scheme here
+=20