Building a release for vote:
- Grab a clean checkout for safety.
- Run: “git checkout ${BRANCH}” if needed to switch to branch of the intended release point.
- Update the versions etc:
- VERSION.txt
- management/python/setup.py
- docs/man/qpidd.1 (and the date)
- src/amqp.cmake (ensure current proton release is marked tested)
- Commit the changes, tag them.
- Run: “git add .”
- Run: ‘git commit -m “update versions for ${TAG}”’
- Run: ‘git tag -m “tag ${TAG}” ${TAG}’
- Run: “bin/export.sh $PWD ${TAG}” to create the qpid-cpp-${VERSION}.tar.gz release archive.
- Create signature and checksum files for the archive:
- e.g “gpg --detach-sign --armor qpid-cpp-${VERSION}.tar.gz”
- e.g “sha512sum qpid-cpp-${VERSION}.tar.gz > qpid-cpp-${VERSION}.tar.gz.sha512”
- Push branch changes and tag.
- Also update versions to the applicable snapshot version for future work on it.
- Commit artifacts to dist dev repo in https://dist.apache.org/repos/dist/dev/qpid/cpp/${TAG} dir.
- Send vote email, provide links to dist dev repo and JIRA release notes.
After a vote succeeds:
- If needed, tag the RC bits with the final name/version.
- Commit the artifacts to dist release repo in https://dist.apache.org/repos/dist/release/qpid/cpp/${VERSION} dir:
- Give the mirrors some time to distribute things. Usually 24hrs to be safe, less if needed.
- Update the website with release content.
- Send release announcement email.