Page History

...

The policy on releasing artifacts from an incubating Apache project is stated in the Guide to Release Management During Incubation. If any stated tasks in this document conflict with what is stated in the policy document, it must be brought to the notice of PPMC for further resolutionWhile Flume is now a top-level project, that guide is still a good resource for new release managers since it contains what are considered to be best practices.

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

...

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.0.0'.

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

...

the version being released.

Since the JIRA release note tool will pull in all JIRAs associated with a particular fixVersion, regardless of their Resolution, you may want to remove fixVersion on issues declared as "Duplicate", "Won't Fix", "Works As Expected", etc. You can use this query to find those issues, then just bulk edit them and leave the fixVersion field blank when editing them.

Project = Flume and Status != Unresolved AND Resolution != fixed AND fixVersion is empty

Finally, look at 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 that the umbrella issue is filed to the time when 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.

...