| Author |
 Topic  |
|
|
Astralis
Senior Member
USA
1218 Posts |
 Posted - 30 November 2003 : 18:37:06
|
Is there a standard to software version numbers?
Google didn't turn up anything to this question except for sarcastic computer coders creating their own little schemes.
From the Beta, to the Full Release, to updates, etc... is there a standard in the software industry to numbering each version? Or do most companies create their own format?
If there is a standard, what is it? |
|
|
dayve
Forum Moderator
USA
5820 Posts |
Posted - 30 November 2003 : 18:50:42
|
| no, I don't believe there are any standards at all for this. |
 |
 |
|
|
HuwR
Forum Admin
United Kingdom
20585 Posts |
Posted - 30 November 2003 : 19:00:39
|
in general they go something like
majorversion.minorversion.releasenumber.buildnumber |
|
|
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 01 December 2003 : 11:41:49
|
| Could you define a "release number" and a "build number"? |
|
|
|
HuwR
Forum Admin
United Kingdom
20585 Posts |
Posted - 01 December 2003 : 11:57:53
|
ok, this forum is version 3.4.03, 03 being the third release of version 3.4
a build number would relate to a compiled program, and would indicate the number of time the executable had been fully compiled |
|
|
|
dayve
Forum Moderator
USA
5820 Posts |
Posted - 01 December 2003 : 16:21:57
|
| How do you decide whether or not you have made a major version change? |
|
|
|
|
HuwR
Forum Admin
United Kingdom
20585 Posts |
Posted - 01 December 2003 : 16:27:14
|
quote:
Originally posted by dayve
How do you decide whether or not you have made a major version change?
That's entirely up to you really, depends on your planned development strategy. |
|
|
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 01 December 2003 : 16:28:32
|
| I guess that would be relative to the project and therefore the company or project manager decides based on inter-office guidelines. Correct? Or is it all just a whim? |
|
|
|
davemaxwell
Access 2000 Support Moderator
USA
3020 Posts |
Posted - 01 December 2003 : 17:14:26
|
It's kinda a whim, but not really. It all depends on the scale of changes being made to a product.
If you're making minor changes, then you issue a release number. 3.4.01, 3.4.02 and 3.4.03 all were bug fixes to the 3.4 release, but no new functionality was added.
If you're making sweeping changes but the core functionality stays the same, then you get a new minor version number. For example, when we switched from the context switching over to the all response.write, that was a major change but the functionality stayed the same, which is why the 3.3 to 3.4 minor version switch was done.
The internationalization is another sweeping change, but it also includes some base functionality changes which is why it'll probably get a new major version number, though that's up to the copyright holders, ie the owners. |
Dave Maxwell
Barbershop Harmony Freak |
|
|
| |
Topic |
|
Topic Locked
