on master help sign in
Clarify which build package removing will occur in.
commitfb526f51c6db8284f2e084b2c64cf58b04aff0e3 authorLuke Murphy <lukewm@riseup.net> dateSat 28 Jan 2017, 20:53 (10 years ago) parenta18238a
1 file changed+3−3
CURATORS.md+3−3
CURATORS.md+3−3
@@ -353,8 +353,8 @@ will upgrade their packages to allow for the new GHC release.
353353We prefer to prune packages causing upper bounds constraints **after** the LTS
354354release to allow the maximum amount of packages to get into the newest LTS.
355355
356−After the first LTS release, the package pruning process may begin in order to
357−move forward with getting the latest versions of packages compatible with the
358−new GHC release.
356+After the first LTS release, the package pruning process may begin in the
357+nightly build in order to move forward with getting the latest versions of
358+packages compatible with the new GHC release.
359359
360360[GHC upgrade note]: https://github.com/fpco/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version