Rumperuu/footnotes
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Removed p codebase tag steps, clarified instructions.

Ben Goldsworthy 2021-03-15 18:45:17 +00:00
parent 7015bc43e2
commit e4e6846efa
1 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
Versioning.md

@ -14,18 +14,23 @@ On top of this, **footnotes** version identifiers can be appended with one of tw
- e.g., ‘2.5.2d’
- 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`
- There is no need to individual number development releases
- `p`, indicating a pre-release
- e.g., ‘2.5.2p’
- This should only be found on the SVN repo.
- 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`
So, to summarise:
- if 2.5.1 is the latest stable release available on the SVN repo. (from `tags/2.5.1/`);
- the codebase in the `main` branch on the Git repo. should be tagged as 3.0.0d, 2.6.0d or 2.5.2d;
- the codebase in `trunk/` on the SVN repo. should be 2.5.1 and identical to the release in `tags/2.5.1/`; OR
- 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 codebase in the `main` branch on the Git repo. is 3.0.0d, 2.6.0d or 2.5.2d;
- the codebase in `trunk/` on the SVN repo. is either:
- 2.5.1 and identical to the release found in `tags/2.5.1/`; OR
- 3.0.0p, 2.6.0p or 2.5.2p.
- the ‘Stable Tag’ field in `trunk/readme.txt` will 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, remove the `p` flag, copy `trunk/` to `tags/<new-version>/` and update the ‘Stable Tag’ field in `trunk/readme.txt` to point to <new-version>.
IN SHORT: There is only ever one `d` and one `p` codebase for a given version. 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 (i.e. `p` receives no additional features or bugfixes, just whatever needs to be done to make the already-implemented ones work if necessary).
IN SHORT: There is only ever one `d` and one `p` codebase. The `d` codebase continuously changes until it is ready to be frozen as a `p` codebase and pre-released to `trunk/`. The `p` codebase then continuously changes (but hopefully not much) until it ready to be frozen as a full release (i.e., the `p` codebase should receive no additional features or bugfixes, just whatever needs to be done to make the already-implemented ones work correctly if there are issues).
IN EVEN SHORTER: `d` codebases should live as long as they need to. `p` codebases should be short-lived.