You are here: Foswiki>Tasks Web>Item15148 (06 Aug 2023, MichaelDaum)Edit Attach

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

pencil
Priority: Enhancement
Current State: Closed
Released In: 2.1.8
Target Release: patch
Applies To: Engine
Component:
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 $Foswiki.pm 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/build.pl massively.

-- MichaelDaum - 17 Jun 2022

 
Topic revision: r5 - 06 Aug 2023, 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