Can we start following some type of version guidelines? That is to say, Version can be broken down into 4 components.
1.2.3 (4)
1. is a major version enhancement, we modify this number by 1 whenever a major new feature or enahcment is implemented.
2. is modified when a minor feature is implemented, or optomizations, ect.
3 is modified when a bugfix, or typo or some slight improvement.
4 is either alpha/beta, post alpha, post beta, or in case of a finished product part 4 of version information is not present.
It makes it alot easier for others to follow whats going on. going from 0.2.3, 0.2.4, 0.2.5 in sequence makes no since, except that its a new release.
++Cire.
Version
- zuzuf
- Administrateur - Site Admin
- Posts: 3281
- Joined: Mon Oct 30, 2006 8:49 pm
- Location: Toulouse, France
- Contact:
Yes, current version is very different from previous release. There are lots of optimizations and lots of things have been rewritten. But we will release a 0.3.0 and when replacing the sound system we will have to set it to 0.4.0...
I see things like this:
1.2.3 (4)
1: 0 for now until it gets to a functional release with working network play and AI and nice GUI (very important), then it will be 1 until we break compatibility with previous version (for networking for example, ...)
2: the subversion number is used to specify current objectives at short term: AI, networking, sound system, ...
3: tell how far we get into our short term objectives
4: bug fixes, beta test releases
So we will release 0.3.0 for Christmas instead of 0.2.4, but next release with new sound system will be 0.3.1 since objectives for 0.3.x are: rewriting what has to be rewritten and start AI and networking support (planned to be functional for 0.4.0).
I see things like this:
1.2.3 (4)
1: 0 for now until it gets to a functional release with working network play and AI and nice GUI (very important), then it will be 1 until we break compatibility with previous version (for networking for example, ...)
2: the subversion number is used to specify current objectives at short term: AI, networking, sound system, ...
3: tell how far we get into our short term objectives
4: bug fixes, beta test releases
So we will release 0.3.0 for Christmas instead of 0.2.4, but next release with new sound system will be 0.3.1 since objectives for 0.3.x are: rewriting what has to be rewritten and start AI and networking support (planned to be functional for 0.4.0).
=>;-D Penguin Powered
Who is online
Users browsing this forum: No registered users and 13 guests