Update doc/MAINTAINER_GUIDE.md

Author: borsboom

doc/MAINTAINER_GUIDE.md

@@ -5,11 +5,14 @@
 The following should be tested minimally before a release is considered good
 to go:
 
+* After GHC 8.0: switch to Debian 8 and CentOS 6.7 Vagrant boxes for building Stack
+  binaries (to match GHC bindists) and drop support for Debian 7.
 * Ensure `release` and `stable` branches merged to `master`
 * Integration tests pass on a representative sample of platforms: `stack install
   --pedantic && stack test --pedantic --flag stack:integration-tests` . The actual
   release script will perform a more thorough test for every platform/variant
   prior to uploading, so this is just a pre-check
+* Ensure `stack haddock` works
 * Stack builds with `stack-7.8.yaml` (Travis CI now does this)
 * stack can build the wai repo
 * Running `stack build` a second time on either stack or wai is a no-op
@@ -22,6 +25,7 @@ to go:
         * Rename the "unreleased changes" section to the new version
         * Check for any entries that snuck into the previous version's changes
           due to merges
+        * Check the Git log for any Changelog entries that were missed
 * In master branch:
     * Bump version to next odd second-to-last component
     * Add new "unreleased changes" secion in changelog
@@ -103,42 +107,10 @@ for requirements to perform the release, and more details about the tool.
       * Be sure to update the SHA sum
       * The commit message should just be `haskell-stack <VERSION>`
 
-* [Build new MinGHC distribution](#update-minghc)
-
 * Keep an eye on the
   [Hackage matrix builder](http://matrix.hackage.haskell.org/package/stack)
 
 * Announce to [email protected], [email protected],
   [email protected] mailing lists
 
 * Merge any changes made in the RC/release/stable branches to master.
-
-## Extra steps
-
-### Update MinGHC
-
-Full details of prerequisites and steps for building MinGHC are in its
-[README](https://github.com/fpco/minghc#building-installers). What follows is an
-abbreviated set specifically for including the latest stack version.
-
-* Ensure `makensis.exe` and `signtool.exe` are on your PATH.
-* If you edit build-post-install.hs, run `stack exec -- cmd /c build-post-install.bat`
-* Set `STACKVER` environment variable to latest Stack verion (e.g. `0.1.10.0`)
-* Adjust commands below for new GHC versions
-* Run:
-
-```
-del .build\*.nsi
-stack build
-stack exec -- minghc-generate 7.10.2 --stack=%STACKVER%
-signtool sign /v /n "FP Complete, Corporation" /t "http://timestamp.verisign.com/scripts/timestamp.dll" .build\minghc-7.10.2-i386.exe
-stack exec -- minghc-generate 7.10.2 --arch64 --stack=%STACKVER%
-signtool sign /v /n "FP Complete, Corporation" /t "http://timestamp.verisign.com/scripts/timestamp.dll" .build\minghc-7.10.2-x86_64.exe
-stack exec -- minghc-generate 7.8.4 --stack=%STACKVER%
-signtool sign /v /n "FP Complete, Corporation" /t "http://timestamp.verisign.com/scripts/timestamp.dll" .build\minghc-7.8.4-i386.exe
-stack exec -- minghc-generate 7.8.4 --arch64 --stack=%STACKVER%
-signtool sign /v /n "FP Complete, Corporation" /t "http://timestamp.verisign.com/scripts/timestamp.dll" .build\minghc-7.8.4-x86_64.exe
-```
-
-* Upload the built binaries to a new Github release
-* Edit [README.md](https://github.com/fpco/minghc/blob/master/README.md#using-the-installer) and update download links