[GRASS5] Roadmap: Numbering

[Buchan Milne]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Markus Neteler wrote:
> On Tue, Aug 12, 2003 at 07:28:43PM +0100, Paul Kelly wrote:

>
> According to this suggestion I have updated the roadmap:
> http://grass.itc.it/roadmap.html

As a mostly-user of grass, I get confused by this. Where was 5.2? Why no
5.1 if there is a 5.3? What about 5.7 if there is a 5.8?

The other software I am familiar with that has a similar problem with
versioning is samba. They had a stable release branch, 2.0.x, and were
doing heavy development in HEAD, which was supposed to be 2.1. Then,
they realised they would need a new stable branch with selected features
from HEAD (win2k support when a domain controller). So, they renumbered
HEAD to 3.0, but the new stable release branch became 2.2.x.

Grass is in a similar position. I would suggest, to keep people from
wondering about seemingly random version numbers, to:

- -keep 5.0.x branch in bugfix mode
- -development of current grass50 cvs becomes 5.1, if pre-release
snapshots are to be made, eventually becoming 5.2.x
- -current grass51 becomes 5.3 (if pre-releases are made), and eventually
becomes either 5.4 or 6.0, depending on circumstances.

There's nothing wrong with going from 5.2 to 6.0, but I find
5.0->5.4->5.8->6.0 a bit weird.

Of course, I am just a user ...

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/O5qurJK6UGDSBKcRAtj9AJ9l866hnj2gvBTaTacYJJT69LYB8QCeInxB
Z9jy79+gzuUtwOwJ5LG0x2Q=
=Rmxu
-----END PGP SIGNATURE-----

******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to info at cae.co.za for a copy.
******************************************************************