As a rabblerouser system administrator, I want the installation process to give me a collection of each component, tested to work together, so that I know that what I am installing is compatible with each other.

[tomsulston]

Background:

When deploying, we should be pinned to specific versions of each component. Not just 'latest'.

Technical notes:

Put the deployables into a versioned S3 bucket? Use a manifest that gets from a variety of sources?

[ineffyble]

Would we want to maintain multiple release channels? (e.g. Google Chrome has "stable", "beta", "dev", and "canary")

[camjackson]

Release channels sounds like a good idea longer term. I think for this particular issue we have more basic stuff that we don't even do yet. E.g. versioning our artefacts at all, and being able to select a set of versions when deploying. Right now everything is bleeding edge.

[ineffyble]

Using Docker image tags for "stable" and "beta" in addition to the default "latest" could be a good simple step.

We could potentially link those to git tags. Although I'm not sure if having git tags that regularly move forward (as opposed to for fixed points in time) is a best practice.