1.9b = 2.0?
Moderators: Jay2k1, DavidM, The_One
1.9b = 2.0?
Just noticed that the change log no longer shows 1.9b but 2.0 instead. (unless I've had a brainfart and it never said 1.9b)
When did this happen and does that mean a longer wait? (I don't mind either way)
When did this happen and does that mean a longer wait? (I don't mind either way)
Last edited by The_One on 11-03-2004 21:46, edited 1 time in total.
nah, changes log is old, from times where 1.9b was not planned.
current log is in some of the latest news details
we cannot release 1.9b as 2.0 because this number requires some major stuff, and we arent that far yet.
but dont expect 1.9c
current log is in some of the latest news details
we cannot release 1.9b as 2.0 because this number requires some major stuff, and we arent that far yet.
but dont expect 1.9c

Last edited by DavidM on 11-03-2004 23:57, edited 1 time in total.
Best way to do version nos. is in 3 parts:
major.minor.patch
eg 2.4.24
A small (or even large) bugfix gets a patch increment.
A change that adds new features gets a minor level.
A change that breaks compatibility with older versions, or a complete rewrite gets a major level.
Not quite sure how that adapts to db, but it seems to me that the version referred to as 1.9b, really ought to be 1.10.
major.minor.patch
eg 2.4.24
A small (or even large) bugfix gets a patch increment.
A change that adds new features gets a minor level.
A change that breaks compatibility with older versions, or a complete rewrite gets a major level.
Not quite sure how that adapts to db, but it seems to me that the version referred to as 1.9b, really ought to be 1.10.
- Catalyst88
- Posts: 707
- Joined: 18-03-2003 12:02
- {UFO}Viper
- Member
- Posts: 56
- Joined: 26-07-2003 09:32
-
- Junior Member
- Posts: 22
- Joined: 12-01-2004 17:44
- Contact:
-plær- wrote: Best way to do version nos. is in 3 parts:
major.minor.patch
eg 2.4.24
A small (or even large) bugfix gets a patch increment.
A change that adds new features gets a minor level.
A change that breaks compatibility with older versions, or a complete rewrite gets a major level.
Not quite sure how that adapts to db, but it seems to me that the version referred to as 1.9b, really ought to be 1.10.
I disagree with the 1.10... version numbers should be looked at as float numbers.
1.9b should either be 1.9.1, or it should be looked at as 1.91
I believe this method causes less confusion. (Remember Windows 3.11). (I prefer 1.9.1)