... | ... | @@ -11,9 +11,13 @@ GHC releases fall into two categories: |
|
|
* **major releases** carry version number `N.M.1` and may include major new features and breaking changes.
|
|
|
* each major release is followed by zero or more **minor releases**. These will typically only contain bug-fixes.
|
|
|
|
|
|
Major releases are currently produced twice a year. Each major release is preceded by a series of **pre-releases** which allow GHC's developers and users to test the release. This prerelease window typically lasts three months and consists of several **alpha releases** followed by a **release candidate**, (hopefully) followed by the final release.
|
|
|
Major releases are currently produced twice a year. The schedule for a major release looks like this:
|
|
|
* **Fork**: a branch in the repository is created, named for the release, e.g. `ghc-9.8`
|
|
|
* **Alpha releases**: a series of pre-releases, called `alpha 1`, `alpha 2`, etc, allow GHC's developers and users to test the release. This prerelease window typically lasts three months.
|
|
|
* **Release candidate** is a release is supposed to be ready to go. Sometimes there is a quick succession of release candidates as minor glitches are fixed called `RC1`, `RC2`, etc.
|
|
|
* **Final release**.
|
|
|
|
|
|
Minor releases generally occur on an as-needed basis without a pre-determined schedule.
|
|
|
Minor releases generally occur on an as-needed basis without a pre-determined schedule. But once we have decided to make a minor release, we post the schedule on the milestone.
|
|
|
|
|
|
|
|
|
## Major release series
|
... | ... | |