Updated Versioning (markdown)
parent
9f70dd5682
commit
e1bb58b831
1 changed files with 3 additions and 1 deletions
|
@ -26,4 +26,6 @@ So, to summarise:
|
||||||
- the codebase in `trunk/` should be tagged as 3.0.0p, 2.6.0p or 2.5.2p, with the pre-release copied to `tags/3.0.0p/`, `tags/2.6.0p/` or `tags/2.5.2p/`; and
|
- the codebase in `trunk/` should be tagged as 3.0.0p, 2.6.0p or 2.5.2p, with the pre-release copied to `tags/3.0.0p/`, `tags/2.6.0p/` or `tags/2.5.2p/`; and
|
||||||
- the ‘Stable Tag’ field in `trunk/readme.txt` should continue to point to `tags/2.5.1`.
|
- the ‘Stable Tag’ field in `trunk/readme.txt` should continue to point to `tags/2.5.1`.
|
||||||
|
|
||||||
When a pre-release version is confirmed to be stable, rename the folder in `tags/` to remove the `p` flag and update the ‘Stable Tag’ field in `trunk/readme.txt`.
|
When a pre-release version is confirmed to be stable, rename the folder in `tags/` to remove the `p` flag and update the ‘Stable Tag’ field in `trunk/readme.txt`.
|
||||||
|
|
||||||
|
IN SHORT: There is only ever one `d` and one `p` codebase. The current `d` codebase changes until it is ready to be frozen as a `p`, and then the `p` codebase changes until it ready to be frozen as a full release.
|
Reference in a new issue