You are here: Foswiki>Tasks Web>Item15148 (22 Jun 2022, MichaelDaum)Edit Attach

Item15148: core's RELEASE and VERSION scheme should follow standards established in skins and extensions

Priority: Enhancement
Current State: Waiting for Release
Released In: 2.1.8
Target Release: patch
Applies To: Engine
Branches: Release02x01 master
Reported By: MichaelDaum
Waiting For:
Last Change By: MichaelDaum
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.

Proposed change:

  • do not auto-commit anything
  • store the date when the release happened in RELEASE as extensions do

This will simplify tools/ massively.

-- MichaelDaum - 17 Jun 2022


ItemTemplate edit

Summary core's RELEASE and VERSION scheme should follow standards established in skins and extensions
ReportedBy MichaelDaum
SVN Range
AppliesTo Engine
Priority Enhancement
CurrentState Waiting for Release
Checkins distro:5cfc08dd12d9 distro:8bd1d955bbe4 distro:eff6629cb170 distro:1eb362c2e1d3
TargetRelease patch
ReleasedIn 2.1.8
CheckinsOnBranches Release02x01 master
masterCheckins distro:8bd1d955bbe4 distro:eff6629cb170
Release02x01Checkins distro:5cfc08dd12d9 distro:1eb362c2e1d3
Topic revision: r4 - 22 Jun 2022, MichaelDaum
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy