...

Update CHANGES.txt in trunk to replace Trunk (unreleased changes) with Release X.Y.0 - YYYY-MM-DD. Commit:
No Format
svn commit -m "Preparing for release X.Y.Z"

Create a branch for the release series:

No Format
svn copy https://svn.apache.org/repos/asf/incubator/bigtop/trunk \ https://svn.apache.org/repos/asf/incubator/bigtop/branches/branch-X.Y -m "Branching for X.Y releases"

Bump the version number in trunk:

No Format
for file in $(find . -name pom.xml); do sed -i -e "s/0.X.0-incubating-SNAPSHOT/0.Y.0-incubating-SNAPSHOT/" $file; done

Checkout the release branch

No Format
svn checkout https://svn.apache.org/repos/asf/incubator/bigtop/branches/branch-X.Y

Update the release branch's version information: the version number in the release branch ends in -SNAPSHOT, but we need to remove this for the release. For example, 0.1.0-incubating-SNAPSHOT needs to be changed to 0.1.0-incubating.
No Format
for file in $(find . -name pom.xml); do sed -e "s/0.X.Y-incubating-SNAPSHOT/0.X.Y-incubating/" $file; done

Commit these changes to the release branch

No Format
svn commit -m "Changing version to 0.X.Y-incubating"

3.

...

TODO

...

Generate the Release Notes

JIRA has the ability to generate release notes automatically (this is why it is so important to keep the fix version number accurate).

...

Wrap the title ("Release Notes - Bigtop - Version X.Y.Z") inside an <h1> element.

TODO

...