Updated Versioning (markdown)
parent
e4e6846efa
commit
33c816ac08
1 changed files with 2 additions and 1 deletions
|
@ -14,11 +14,12 @@ On top of this, **footnotes** version identifiers can be appended with one of tw
|
||||||
- e.g., ‘2.5.2d’
|
- e.g., ‘2.5.2d’
|
||||||
- This should **only** be found on the Git repo.
|
- This should **only** be found on the Git repo.
|
||||||
- The version number should **always** be one higher than the version number listed in the ‘Stable Tag’ field in `readme.txt`
|
- The version number should **always** be one higher than the version number listed in the ‘Stable Tag’ field in `readme.txt`
|
||||||
- There is no need to individual number development releases
|
- There are no individually-numbered development releases
|
||||||
- `p`, indicating a pre-release
|
- `p`, indicating a pre-release
|
||||||
- e.g., ‘2.5.2p’
|
- e.g., ‘2.5.2p’
|
||||||
- This should **only** be found on the SVN repo. in `trunk/`
|
- This should **only** be found on the SVN repo. in `trunk/`
|
||||||
- The version number should **always** be one higher than the version number listed in the ‘Stable Tag’ field in `readme.txt`
|
- The version number should **always** be one higher than the version number listed in the ‘Stable Tag’ field in `readme.txt`
|
||||||
|
- There are no individually-numbered pre-releases
|
||||||
|
|
||||||
So, to summarise:
|
So, to summarise:
|
||||||
|
|
||||||
|
|
Reference in a new issue