Packaging

Repositories

We have four different Packagecloud (RPM/Deb) package repositories:

Environment	staging	production
unstable	1	2
stable	3	4

Code gets promoted through the following repositories:

1. StackStorm/staging-unstable - the current state of master; packages built, tested, and pushed directly to Packagecloud by CircleCI
2. StackStorm/unstable - latest master that passed end-to-end tests and promotion workflows at the scheduled daily time; packages are promoted in the st2ci daily/nightly runs
3. StackStorm/staging-stable - current “release candidate”, aka the latest commit on a release branch (should only change while a release is actively taking place); done during the pre-release testing process by st2cd workflows (IIRC), before last minute tests
4. StackStorm/stable - tagged releases, i.e. 3.0, 3.1, 3.1.1 - should only get updated when there is a release; packages are promoted automatically by st2cd workflows