Page History

...

4. Find hash for use later

git log

5. Create a branch for the X.(Y+1) release series

E.g. flume-1.5 should be branched off of flume-1.4

git checkout flume-X.Y

...

git checkout -b flume-X.(Y+1)

...

git cherry-pick <hash from the previous step>

6. Push the changes up stream

git push -u origin trunk:trunk

...

git push -u origin flume-X.Y:flume-X.Y

7. Checkout the release branch:

git checkout flume-X.Y

8. Remove -SNAPSHOT from the release branch and commit

find . -name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.Y.0/"

...

find flume-ng-doc/ -name "*.rst" | xargs  sed -i "" -e "s/X.Y.0-SNAPSHOT/X.Y.0/"

...

git add .

...

git commit -m "FLUME-XXXX: Removing -SNAPSHOT from X.Y branch"

9. Ensure RELEASE-NOTES has the appropriate version and description of the release.

...

cd flume-ng-dist/target
tar xzvf apache-flume-1X.0Y.0Z-src.tar.gz

4. Do another full build inside the source tarball. This time, allow all unit tests & integration tests to run

cd apache-flume-1X.0Y.0Z
mvn clean install

Signatures and Checksums

...