... | ... | @@ -2,8 +2,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
|
|
|
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 canonical release schedule. Meanwhile the tracking ticket contains internal bookkeeping and a chronological account of the current status of the release.
|
... | ... | |