release.hs: reorganize distro packacing to use vagrant instead of Docker

Author: borsboom

doc/MAINTAINER_GUIDE.md

@@ -1,8 +1,8 @@
 The following should be tested minimally before a release is considered good
 to go. This list will likely expand over time:
 
-* Run `scripts/release/release.hs check` on Linux (32-bit and 64-bit), Windows (`--arch=i386` and `--arch=x86_64`), and OS X. See its
-  [README](https://github.com/commercialhaskell/stack/blob/master/scripts/release/README.md) for build and invocation instructions.
+* Run `etc/scripts/release.hs check` on Linux (32-bit and 64-bit), Windows (`--arch=i386` and `--arch=x86_64`), and OS X. See its
+  [README](../etc/scripts/README.md#release.hs) for build and invocation instructions.
   This performs the following checks automatically:
     * `stack install && stack clean && stack install --pedantic && stack test --flag stack:integration-tests` on Linux, Windows, and OS X, which covers:
         * Self-hosting
@@ -20,11 +20,11 @@ to go. This list will likely expand over time:
 Release checklist after testing:
 
 * Create a draft Github release with tag `vX.Y.Z` (where X.Y.Z is the stack package's version).
-* Run `scripts/release/release.hs release` on Linux (Debian 7 32-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-i386)/64-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-amd64)), Windows (`--arch=i386` and `--arch=x86_64`), and OS X.  This performs the following tasks automatically:
+* Run `etc/scripts/release.hs release` on Linux (Debian 7 32-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-i386)/64-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-amd64)), Windows (`--arch=i386` and `--arch=x86_64`), and OS X.  This performs the following tasks automatically:
     * Binaries for Linux, Windows, and OS X uploaded to draft Github release.
-* Run `scripts/release/release.hs --binary-variant=gmp4 release` on CentOS 6 32-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/centos-6-i386)/64-bit [Vagrantfile](centos-6-x86_64)).
-* Run `scripts/release/release.hs ubuntu-upload debian-upload` in Linux (Ubuntu or Debian - [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-amd64))
-* Run `scripts/release/release.hs centos-upload fedora-upload` on Linux (CentOS or Fedora - [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/centos-7-x86_64))
+* Run `etc/scripts/release.hs --binary-variant=gmp4 release` on CentOS 6 32-bit [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/centos-6-i386)/64-bit [Vagrantfile](centos-6-x86_64)).
+* Run `etc/scripts/release.hs ubuntu-upload debian-upload` in Linux (Ubuntu or Debian - [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/debian-7-amd64))
+* Run `etc/scripts/release.hs centos-upload fedora-upload` on Linux (CentOS or Fedora - [Vagrantfile](https://github.com/commercialhaskell/stack/tree/master/etc/vagrant/centos-7-x86_64))
 * Upload Arch Linux packages (manual process)
 * Build new MinGHC distribution (See https://github.com/fpco/minghc/commit/51490f398e6722672364548a3855a0bfcba48ffe)
 

scripts/release/README.md renamed to etc/scripts/README.md

@@ -1,5 +1,5 @@
-Stack release tool
-==================
+release.hs
+==========
 
 This tool automates some aspects of releasing a new version of Stack. It
 currently handles some tasks that need to be performed on each platform:
@@ -16,6 +16,7 @@ These must be installed in the PATH to use the release tool:
 
 - stack
 - git (for Windows, [msysgit](https://msysgit.github.io) is recommended).
+- cabal (cabal-install)
 
 To create a signed binary, you need:
 
@@ -34,24 +35,26 @@ To upload a binary to a Github release, you also need:
 
 To create and upload Debian/Ubuntu packages, you need:
 
-- Docker installed.
 - deb-s3 installed (`sudo gem install deb-s3`).
 - `[email protected]` secret key in GPG keyring.
 - Set `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment variables with
   credentials that allow uploading to download.fpcomplete.com S3 bucket.
 
 To create and upload Red Hat/CentOS packages, you need:
 
-- Docker installed.
-- rpm-s3 installed (see https://github.com/crohr/rpm-s3).
+- [rpm-s3 installed](https://github.com/crohr/rpm-s3).
 - `[email protected]` secret key in GPG keyring.
 - Set `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment variables with
   credentials that allow uploading to download.fpcomplete.com S3 bucket.
 
+To create and upload Arch packages, you need:
+
+- [AWS CLI installed](http://docs.aws.amazon.com/cli/latest/userguide/installing.html).
+
 Invocation
 ----------
 
-Usage: `scripts/release/release.hs [OPTIONS] TARGET`
+Usage: `etc/scripts/release.hs [OPTIONS] TARGET`
 
 The tool must be run in the root of the working tree.