THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block |
---|
export GPG_TTY=$(tty) mvn clean install -Pfull-build -Papache-release -DskipTests |
Manage JiRA issues
- In Jira, move open issues to next version. Disable mail notifications for this bulk change. If you are in doubt as on dev@zookeeper.apache.org mailing list before proceedig
Create a branch (when you create X.Y.0 and move master to X.Y+1.0)
...
- removes -SNAPSHOT in all of the pom.xml files (the version is RELEASE_VERSION)
- build the project (even the C client and contrib packages)
- ensures the correct version in C client files (configure.ac, CMakelink.txt, TODO zookeeper_version.h)
- created a signed tag
- bump the branch to the next minor version (RELEASE_DEVELOPMENT_VERSION)
Checklist
Make sure the version number is correct in zookeeper-client/zookeeper-client-c/configure.ac, zookeeper-client/zookeeper-client-c/CMakeLists.txt, and zookeeper-client/zookeeper-client-c/include/zookeeper_version.h
Commit these changes.
Code Block | ||
---|---|---|
| ||
# check for modified files
git status
# add modified files one by one
git add <modified files>
# commit and push the changes to remote repo branch-X.Y-X
git commit -m "Preparing for release $VERSION"
git push <remote> branch-X.Y.Z |
Run spotBugs, checkstyle and rat checks:
Code Block |
---|
git clean -xdf
mvn clean apache-rat:check -DskipTests -Pfull-build
mvn clean install checkstyle:check spotbugs:check -DskipTests -Pfull-build |
Preparing the release candidate
...