Item15148: core's RELEASE and VERSION scheme should follow standards established in skins and extensions
Current State: Waiting for Release
Released In: 2.1.8
Target Release: patch
Applies To: Engine
Branches: Release02x01 master
Plugins and skins use
- VERSION: a version id, mostly float (1.23) or a tripple dot version (1.2.3)
- RELEASE: the date when this extension was released
The Foswiki core, as stored in
uses the same value in VERSION and RELEASE - for final releases.
Any pre-release or beta version will diverge using an suffix indicating a test, beta, etc.
What is more disturbing is that the script building the release is auto-commiting the created RELEASE to git.
This caught me once during the 2.1.7: it automatically committed a 2.1.8 RELEASE string for the 2.1.7 VERSION.
- do not auto-commit anything
- store the date when the release happened in RELEASE as extensions do
This will simplify
- 17 Jun 2022