Version numbering (was: [GRASS5] Branching for 5.0.0 ahead)

[Carl Worth]

On Apr 23, Bernhard Reiter wrote:
 > We've decided some time ago to try to adapt the Linux kernel
 > version numbering scheme.
 > 
 > Thus we have a stable line: 5.0.x
 > and a development line: 5.1.x
 > Next stable line will be 5.2.x

Bernhard,

Let me summarize things the way I see it to make sure I've got the
plan straight:

1) If users stick to a release that has an even number as the second
   component in the version, they can rest assured that upgrading
   across minor versions, (eg. 5.0.1 to 5.0.2), will not cause
   incompatibilities to be introduced.

2) If a developer wants to introduce and incompatible change, the
   change must take place on the development line with an odd-numbered
   second component, (eg. 5.1).

Am I correct? As far as a system for naming what code gets released,
this seems like a good, working system.

Now, a separate issue entirely, is the system used to develop/manage
the code base, (as opposed to naming it). I think we need some
discussion here, so I'll write something up in a separate email.

-Carl

-- 
Carl Worth                                        
USC Information Sciences Institute                 cworth at east.isi.edu
3811 N. Fairfax Dr. #200, Arlington VA 22203		  703-812-3725