Page History

...

The change list can be swiped from the JIRA release note tool (use the "text" format for the change log). See JIRA Cleanup above to ensure that the release notes generated by this tool are what you are expecting. Additionally, in the last two releases we have re-ordered the issues to be New Features, Improvements, Bugs, etc as by default the least important items are at the top.

3. Update the "version" value of all pom.xml and in RELEASE-NOTES in trunk to X.(Y+1).0:

vim RELEASE-NOTES
git checkoutadd trunk
find . -name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.$RELEASE-NOTES
git commit RELEASE-NOTES -m "Updating Flume version in RELEASE-NOTES for release X.Y.Z"

4. Create a branch for the X.(Y+1)

...

release series

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

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

4. Update the "version" value of all pom.xml and documentation files in trunk to X.(Y+1).0-SNAPSHOT

/"
vim RELEASE-NOTES
git addcheckout .trunk
gitfind commit. -m "FLUME-XXXX: Preparing for the X.Y release"

4. Find hash for use later

git log

...

name pom.xml | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.$(Y+1)

...

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

git checkout flume-X.Y
git checkout -b flume-X..0-SNAPSHOT/"
find flume-ng-doc/ -name "*.rst" | xargs sed -i "" -e "s/X.Y.0-SNAPSHOT/X.$(Y+1).0-SNAPSHOT/"
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

add .
git commit -m "Updating trunk version to X.$(Y+1).0-SNAPSHOT for Flume X.Y.Z release"

5. Checkout the release branch and remove -SNAPSHOT from the release branch poms and docs and commit7. Checkout the release branch:

git checkout flume-X.Y

8. Remove -SNAPSHOT from the release branch and commit

X.Y

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.

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

7. Push the branching changes upstream

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

8. Tag a release candidate (in the example below, RC1)10. Tag a candidate:

git tag -a release-X.Y.Z-rc1 -m "Apache Flume X.Y.Z release.RC1"
git push origin release-X.Y.Z-rc1

If an rc1, rc2, rc3 etc is needed, delete that tag before creating simply create a new onerc tag:

git tag -d release-X.Y.Z-rc2
git push origin :refs/tags/release-X.Y.Z-rc2

Performing sanity check

1. Check out the candidate tag

git checkout release-X.Y.Z-rc1

2. Generate a tarball

mvn clean install -DskipTests

...