MOD Version Numbering System |
Description: How to handle version numbers when updating your MOD |
Author: wGEric |
Date: Sun Jan 19, 2003 1:24 am |
Type: HowTo |
Keywords: mod, number, numbering, version |
Category: MODifications |
|
MOD Version Numbering System
phpBB uses a modified version of the Linux kernel versioning system (x.y.z), because of this, MODs also need to use this versioning system.
There are three main parts to each version and there can be an optional fourth part. Each version looks something like this x.y.z
The parts of x.y.z
- x - Major Release
This number is used for a major release. Usually this is only increased when backwards compatibility with previous versions is broken or there has been a major overhaul of the code like a rewrite. If this number is 0, then it is considered in development.
- y - Minor Release
y is the minor release number. This is increased when new features or functionality have been added to the code. If this number is odd, then it is considered in development.
- z - Revision Release
This is the revision number. This is increased when bugs or other very minor changes are made. No new features or large code changes have been made when this number is increased.
- Rereleases
The fourth and optional part of the version number is used for rereleases of a version. If a bug fix introduces more bugs or you forgot to add something to a release, then you can do a rerelease. To signify a rerelease, you add a letter, starting at 'a' and ending on 'z', to the end of the version. Like this 1.2.3a or 1.6.5d.
Development Versus Non-development
It was mentioned that if x is 0 (zero) or y is an odd number, then it means that the version is still in development and not a final/stable release. If you are developing your MOD and it is in the alpha or beta stage then you need to have you version state that it is still in development. So examples of development versions are:
0.3.5
0.2.3
0.1.0c
1.1.2a
1.3.7
3.11.15
If x is above 0 and y is an even number, then the version is considered a final/stable release. x and z can be odd and it is still considered a final/stable release. Here are some examples:
1.0.0
1.2.5
3.10.4d
2.2.1
3.0.0
7.6.8g
Each part is its own separate number and not a decimal. That means if you get to 9, then you go to 10. You do not increase the number in front of it. So if z gets to 9 and you make a new release which would increment z, z then goes to 10 and y stays the same. y does not get increased.
1.2.9 -> 1.2.10
This is correct
1.2.9 -> 1.3.0
This is not correct |
|
|