BZFlag Versions
Posted: Wed Sep 17, 2003 4:42 pm
This is just a note for all the users out there, so noone gets confused when the next release comes out.
We have changed how we are doing version numbers for BZ. It's easyer to understand non
.
BZflag version numbers have 3 parts now.
major version. minor version. revision (no more letters ).
Development versions will allways have an ODD minor version.
Release versions will allways have an EVEN minor version.
The revision number is used to represnet changes in a specific minor version line.
so we are currently developing 1.9.xx ( it's at 1.9.1 now ). As we develop and test we will increment the revision as we add new features and reach various "testing" stages ( 1.9.2, 1.9.3 etc.. ). This will help with bug reports as the version number will now let us know more about the version the bug is reported in.
When we are all happy with the version and it's time for the big release. The version number will be changed to 1.10.0, and posted on SourceForge and all the normal build places. We will then go to work on 1.11.xx as a development version. Now if something in 1.10.0 needs to be fixed ( an exploit, or a big bug), we would make a 1.10.01. It would have no new features, just fixes. This should make it so we can't "paint our selves in a corner" with version numbers.
In adition to this, we have added some more info to the version numbers that are displayed in the software.
you will now see verison numbers like this:
1.9.1-W32VC-CVS-20030917
or
1.9.1-linux-gnu-CVS-20030917
the 1.9.1 is the version as described above
The next item is the OS of the build.
Next is a tag that represnets the build type.
for dev. this is "CVS", but it can be "testing" or "release" for others.
The last is the build date. This tells you how old the binary version is.
Servers will also send this info to the client when you log on to a server. It's nice because you an see what OS the server is on.
So don't be sad if you see us talk about 1.10 ( it should be here soon ).
We have changed how we are doing version numbers for BZ. It's easyer to understand non
.BZflag version numbers have 3 parts now.
major version. minor version. revision (no more letters ).
Development versions will allways have an ODD minor version.
Release versions will allways have an EVEN minor version.
The revision number is used to represnet changes in a specific minor version line.
so we are currently developing 1.9.xx ( it's at 1.9.1 now ). As we develop and test we will increment the revision as we add new features and reach various "testing" stages ( 1.9.2, 1.9.3 etc.. ). This will help with bug reports as the version number will now let us know more about the version the bug is reported in.
When we are all happy with the version and it's time for the big release. The version number will be changed to 1.10.0, and posted on SourceForge and all the normal build places. We will then go to work on 1.11.xx as a development version. Now if something in 1.10.0 needs to be fixed ( an exploit, or a big bug), we would make a 1.10.01. It would have no new features, just fixes. This should make it so we can't "paint our selves in a corner" with version numbers.
In adition to this, we have added some more info to the version numbers that are displayed in the software.
you will now see verison numbers like this:
1.9.1-W32VC-CVS-20030917
or
1.9.1-linux-gnu-CVS-20030917
the 1.9.1 is the version as described above
The next item is the OS of the build.
Next is a tag that represnets the build type.
for dev. this is "CVS", but it can be "testing" or "release" for others.
The last is the build date. This tells you how old the binary version is.
Servers will also send this info to the client when you log on to a server. It's nice because you an see what OS the server is on.
So don't be sad if you see us talk about 1.10 ( it should be here soon ).
