... | ... | @@ -17,6 +17,9 @@ Beyond this the interactions with GHC should be fairly minimal: we'll ask you be |
|
|
|
|
|
The following is a proposed revision of our previous policy for synchronizing core libraries prior to GHC releases.
|
|
|
|
|
|
|
|
|
To ensure that GHC releases ship with up-to-date releases of core libraries, we follow this protocol for updating core libraries during the release process:
|
|
|
|
|
|
1. When GHC cuts a feature-freeze branch, the release manager will ask the core library maintainers to cut a feature freeze branch of their libraries. Upon cutting the branch the maintainer should notify the release manager so the GHC submodule can be updated. It is expected that this take no longer than two weeks; if a library maintainer hasn't responded within two weeks GHC will ship with the library version shipped with the most recent GHC release.
|
|
|
1. When GHC cuts a release candidate, the release manager will ask the core library maintainers to make a properly-tagged release of their branches.
|
|
|
|
... | ... | |