;doc: RELEASING: glossary updates, test releases

This commit is contained in:
Simon Michael 2022-01-02 13:07:47 -10:00
parent 51fac9949f
commit ebf4d09537

View File

@ -8,24 +8,25 @@ Tips for hledger release managers and maintainers.
## Glossary ## Glossary
| | | | | |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| |-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| *Full release* | A release of all the core packages (hledger-lib, hledger, hledger-ui, hledger-web) | | *Release* | A named, tagged, documented, usually announced snapshot of the software plus any related artifacts like executable binaries. |
| *Partial release* | A release of only some of the core packages | | *Version number* | A 2-4 part dotted number naming a hledger release, see examples below. For unreleased code it ends with .99, eg a post-1.25 / pre-1.26 build of master will show `1.25.99`. |
| *Mixed release* | A release where some of the core packages have different versions (due to previous partial release) | | *Version string* | A line of text describing a hledger binary, shown by the `--version` flag. It includes the tool name, version number, commit hash and date, machine architecture, etc. |
| *Test release* | A release that is published on github, but not hackage/stackage. These test the release process (and secondly, generate fresh binaries for early adopters) | | *Major release* | Major releases include significant changes like new features and incompatible API changes. hledger major releases normally happen at start of each quarter's last month (Mar 1, Jun 1, Sep 1, Dec 1). Example version number: `1.25` |
| | | | *Minor release* | Minor releases include only bug fixes, without API changes. These happen only when needed, to fix significant bugs in a major release. Example version number: `1.25.2` |
| *hledger repo* | The `hledger` git repository, containing the core hledger tools and docs. Official public copy: github.com/simonmichael/hledger | | *Fixup release* | Fixup releases include only fixes for packaging errors, and no changes to the hledger software. These should be rare. Example version number: `1.25.0.1` or `1.25.2.1` |
| *"master"* | The `master` branch in the hledger repo; the main line of hledger development | | *Test release* | A snapshot of development code, published only on github, not hackage, to exercise the release process and provide fresh binaries for testers/early adopters. These can happen any time but typically at the start of a quarter's first or second month. Example version number: `1.25.20220102` |
| *release branch* | Branches named `MAJORVERSION-branch` in the hledger repo, eg `1.24-branch`. Releases are made from these. | | *Full release* | A release of all the core hledger packages (hledger-lib, hledger, hledger-ui, hledger-web) with all of them using the same version number. Major releases are always full releases. |
| | | | *Partial release* | A release of only some of the core packages. Minor releases are sometimes partial. |
| *site repo* | The `hledger_website` git repository, containing the hledger.org website and additional docs. Usually checked out under the hledger repo as `site/`. | | *Mixed release* | A release where some packages have different versions, because of a previous partial release. Minor releases are sometimes mixed. |
| *"site"* | The `master` branch in the site repo, used to generate <https://hledger.org>. | | *hledger repo* | The `hledger` git repository, containing the core hledger tools and docs. Official public copy: github.com/simonmichael/hledger |
| | | | *"master"* | The `master` branch in the hledger repo; the main line of hledger development |
| *version* | the 2 or 3-part dotted version number that names a hledger release: MA.JOR or MA.JOR.MINOR. | | *release&nbsp;branch* | Branches named `MAJORVERSION-branch` in the hledger repo, eg `1.24-branch`. Releases are made from these. |
| *MAJORVER* | Just the MA.JOR part, eg 1.24 | | *site repo* | The `hledger_website` git repository, containing the hledger.org website and additional docs. Usually checked out under the hledger repo as `site/`. |
| *OLD*, *NEW* | Previous and new pending release versions. Examples: 1.24 -> 1.24.1, 1.24.1 -> 1.24.2, 1.24.2 -> 1.25. | | *"site"* | The `master` branch in the site repo, used to generate <https://hledger.org>. |
| | | | *MAJORVER* | Just the MA.JOR part, eg 1.24 |
| *OLD*, *NEW* | Previous and new pending release versions. Examples: 1.24 -> 1.24.1, 1.24.1 -> 1.24.2, 1.24.2 -> 1.25. |
## 2021-12 ## 2021-12