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

[Bernhard Reiter]

On Tue, Apr 23, 2002 at 02:55:36PM +0000, Carl Worth wrote:
> 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

> 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.

Basically, but with no major incompatibilities.
Like the kernel, they've had _some_ incompatibilities which cannot
be avoided.

> 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).

Basically correct with the same restriction as above.
You could do some changes in the grass5(0) normal branch,
when development is open.

> 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.

Fair enough. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20020423/e6d4d333/attachment.bin