Skip to content

Changes

Page history
Remove sync-all reference authored by thomie's avatar thomie
Hide whitespace changes
Inline Side-by-side
working-conventions/releases.md
View page @ 112498bb
......@@ -66,7 +66,7 @@ See [MakingReleases](making-releases) and [TodoAfterReleases](todo-after-release
The `master` branch of all repositories is the main development branch. We often call this "HEAD" for historical reasons.
There is a **stable branch** corresponding to each major release, named after the major version. For example, the stable branch corresponding to the 7.8 series of releases is called `ghc-7.8`. Every repository (see [Repositories](working-conventions/repositories)) has a `ghc-7.8` branch, so you can switch a complete tree to the branch with `./sync-all checkout ghc-7.8`.
There is a **stable branch** corresponding to each major release, named after the major version. For example, the stable branch corresponding to the 7.10 series of releases is called `ghc-7.10`. Every repository (see [Repositories](working-conventions/repositories)) has a `ghc-7.10` branch, so you can switch a complete tree to the branch with `git checkout ghc-7.10; git submodule update`.
**Releases are only made from the stable branch.** The stable branch for a major release is created by the release manager shortly before the release candidate (a couple of weeks or so). When the release is made, the stable branch (of all repositories) is tagged with the release name, e.g. `ghc-7.8.1`.
......