When Quickstep updates with new functionality or improvements, we release quickstep as a tarball. A release manager is responsible for executing this process.

Release Managers

Release managers is a self-selected committer whose responsibility it is to go through this release process. This involves creating the release artifacts, counting votes, and publishing release artifacts. This is covered in detail below.

...

In this phase, we decide which commits will go into the release. We publish dev artifacts and the community votes if it should progress to a final release. Releases have a version (x.y.z) and candidates have a candidate version (rcX). There can be multiple candidates but only one release. 

a. Make and publish a release candidate

These steps are somewhat covered in the script on Marc Spehlmann's gist. The individual steps below explain what happens in the script. Also, the script must be modified to do some of things covered here. It's a rough guide.

i. Select a commit to base the release

You will create a release branch if this is the first release candidate. Otherwise, checkout the current release branch.

b. Make a vote on the Release Candidate

...