...

NOTE: For the purpose of illustration, this document assumes that the version being released is 1.2.0-incubating, and the following development version will become 1.3.0-incubating

Table of Contents

Prerequisites

...

Policy documents

Frequently asked questions for making Apache releases are available on Releases FAQ page. Guide to Release Management During Incubation also has good information on best practices for releasing artifacts from an incubating Apache project.

The Release Manager (RM) must go through the policy document to understand all the tasks and responsibilities of running a release.

Give a heads up

The RM should first create an umbrella issue and then setup a timeline for release branch point. The time for the day the umbrella issue is created to the release branch point must be at least two weeks in order to give the community a chance to prioritize and commit any last minute features and issues they would like to see in the upcoming release.

The RM should then send the pointer to the umbrella issue along with the tentative timeline for branch point to the developer lists (TODO: Also send to users list once we create one). Any work identified as release related that needs to be completed should be added as a subtask of the umbrella issue to allow users to see the overall release progress in one place.

To: dev@sentry.incubator.apache.org
Subject: Work on $release release has started

ICreated thinka it'stracking timejira to starting thinking about the next release, which would be (jira#) for the Sentry $release. Ifand othersplan agree,to Ibranch willtentatively createon a tracking JIRA.$date. 
 
WouldWhat would you like to see included?
Thanks,
$RM

Sanitize JIRA

1. Before a release is done, make sure that any issues that are fixed have their fix version setup correctly. Run the following JIRA query to see which resolved issues do not have their fix version set up correctly:

   Code Block
   project = sentry and resolution = fixed and fixVersion is empty

   The result of the above query should be empty. If some issues do show up in this query that have been fixed since the last release, please bulk-edit them to set the fix version to '1.2.0'.

2. You can also run the following query to make sure that the issues fixed for the to-be-released version look accurate:

   Code Block
   project = sentry and resolution = fixed and fixVersion = '1.2.0'

3. Finally, check out the output of the JIRA release note tool to see which JIRAs are included in the release, in order to do a sanity check.

Monitor active issues

It is important that between the time the intent to release email is sent and the release branch is created, no experimental or potentially destabilizing work is checked into the trunk. While it is acceptable to introduce major changes, they must be thoroughly reviewed and have good test coverage to ensure that the release branch does not start of being unstable.

...