... | ... | @@ -3,10 +3,8 @@ This page summarises the state of play of GHC's release engineering efforts. |
|
|
## Release practices
|
|
|
|
|
|
Each GHC release has an associated Gitlab
|
|
|
* **milestone**, denoted by the `%` sigil; example %9.8.1
|
|
|
* **tracking ticket**, an issue, denoted by the `#` sigil, bearing the ~"T::release tracking" label; example #23563.
|
|
|
|
|
|
The milestone carries information such as which issues we are expecting to address in the release and the **release schedule**. Meanwhile the tracking ticket contains internal bookkeeping and a chronological account of the current status of the release.
|
|
|
* **Milestone**, denoted by the `%` sigil; example %9.8.1. The milestone carries information such as which issues we are expecting to address in the release and the **release schedule**.
|
|
|
* **Tracking ticket**, an issue, denoted by the `#` sigil, bearing the ~"T::release tracking" label; example #23563. the tracking ticket contains internal bookkeeping and a chronological account of the current status of the release.
|
|
|
|
|
|
GHC releases fall into two categories:
|
|
|
|
... | ... | |