Skip to content

Latest commit

 

History

History
90 lines (79 loc) · 4.86 KB

new-release.md

File metadata and controls

90 lines (79 loc) · 4.86 KB
name about
New release
Tracking the progress on preparing a new release branch

Release check list

At branch time (pre-beta)

  • Create stabilization branch
  • Create a new transifex resource for branch translation
    • Make sure that slug and name both contain LedgerSMB-XX
    • Make sure that the auto-update URL is set
  • Update the .tx/config section name [ledgersmb.LedgerSMB] -> [ledgersmb.LedgerSMB-XX]
  • Update the version number of the 'master' branch:
    • sql/Pg-database.sql
    • package.json
    • In setup.pm, add support to create databases of the version that 'master' becomes
    • In LedgerSMB.pm, increase the $VERSION variable
    • In bin/ledgersmb-server.psgi adjust the version-check regex
    • In locale/LedgerSMB.pot, adjust the Project-Id
    • In t/data/Is_LSMB_running.html, increase the version text
    • Update README.md reference to docker-compose file (both on the branch and on master)
    • Create a new docker-compose branch
  • Add the new version to renovate.json baseBranches

General preparation

Release steps

  • Update Docker image README.md
    • Docker README listing available tags (on all branches!)
  • Change ledgersmb-docker default branch to the new stable release branch (this causes the 'latest' tag in docker to move to the new branch!)
  • Set the release date of the minor series in Changelog
  • Execute the final release procedure as with a regular (patch) release (but use a different release announcement text)

Post release steps: