Before the next release, make sure docker-aut builds on master... or make sure --packages works

[ruebot]

Two parts to this issue:

1. As we add and remove dependencies to our pom.xml, this will break --packages on master. I'm comfortable with this happening on master, since we're actively adding to it. But, once we get close to a release we should make it builds fine. A sane test environment to do this with what is currently docker-aut master. I can add this to the release documentation as a prerequisite.

2. We should change master to dev on docker-aut, and no longer make it the default branch. @lintool, @ianmilligan1 are you fine with me making the latest release the default branch, and also setting it as the default branch on docker-hub?

I'd create the issue over there, but these two items are closely intertwined.

[ruebot]

Another option is to add a script to the TravisCI build to make sure it always works on master 😄

[ruebot]

...err, maybe not since it would just sit at the scala prompt if it was successful. 🤔

[ianmilligan1]

We should change master to dev on docker-aut, and no longer make it the default branch. @lintool, @ianmilligan1 are you fine with me making the latest release the default branch, and also setting it as the default branch on docker-hub?

Fine with me!

[ianmilligan1]

Once the docker-aut testing is added to the release page as a pre-requisite, now that the default branch on docker-aut is set to latest release, this issue is probably closable?

I would add to the release page myself but I was unsure the right place to put language in.

[ruebot]

Done.