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

Step-by-step guide

Links

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

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

Prerequisites:

• Set up your apache email

• Set up your apache gpg key [help]

  • Created a gpg key using your apache username

  • Uploaded it to a keyserver

  • Added it to the KEYS file in both svn repos

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

Overview

1. Release Candidate Phase
   1. Make and publish a release candidate
   2. Vote on the release candidate
      1. IF Vote passes, GOTO 2. ELSE GOTO 1
2. Release Phase
   1. Make and publish release

1. Release Candidate Phase

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.

a. Make and publish a release candidate

This is under construction. A rough idea of what needs to be done can be found in the script on Marc Spehlmann's gist. Modify the header and then use the function 'prep_quickstep' followed by 'publish_rc'.

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