When Quickstep updates with new functionality or improvements, we release quickstep as a tarball.

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.

Step-by-step

...

Release Guide

Links

SVN Repo for release candidates: https://dist.apache.org/repos/dist/dev/incubator/quickstep

SVN Repo for final releases: https://dist.apache.org/repos/dist/release/incubator/quickstep

Prerequisites

...

As a release manager, you have a couple of base steps which will not be repeated after you go through this process once. 

• Set up your apache email

• Set up your apache gpg key [help]

  • Created a gpg pgp key using your apache username. Per Apache, this must be on your hardware.

  • Uploaded it to a public keyserver

  • Added it to the KEYS file in both svn reposthe dev svn repo. Later, you will add it to the rel svn repo

  • [optional] Made sure someone in the group has validated your key

Overview

1. Release Candidate Phase
   1. Make and publish a release candidate
      1. Select a commit to base the release
      2. Branch and tag the commit
      3. Create the release artifacts
      4. Publish the release artifacts to the dev SVN repo
   2. Vote on the release candidate
      1. Send a VOTE email
      2. Wait 72 hours
      3. Send a follow up email with results
      4. IF Vote passes, GOTO 2. ELSE GOTO 1
2. Release Phase
   1. Make and publish release

...

In this phase, we decide which commits will go into the release. You can take the HEAD of MASTER or cherry pick several commits, that's what should be decided in a discussion around a release. Next you will make and publish a release to the dev SVN repo. Then we vote. If the vote passes (majority) then we will move to the Release Phase.We publish dev artifacts and the community votes if it should progress to a final 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.

i. Select a commit to base the release

b. Make a vote on the Release Candidate

Send a [VOTE] to the dev list using your apache email. Explain what version it is and what are the changes. Leave 72 hours for responses to come in. After that has passed, move to the Release Phase.

Related articles

...