From b0f9d72840ec13030ad97ad77bf7478a079c2f6f Mon Sep 17 00:00:00 2001 From: Mick Semb Wever Date: Sat, 21 Sep 2019 18:53:14 +0200 Subject: [PATCH] Add the how and when to perform the step of incrementing the codebase's version into the existing release process documentation patch by Mick Semb Wever; reviewed by Michael Shuler for CASSANDRA-15333 --- doc/source/development/release_process.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/source/development/release_process.rst b/doc/source/development/release_process.rst index b3c403215f..0ab6dff1a4 100644 --- a/doc/source/development/release_process.rst +++ b/doc/source/development/release_process.rst @@ -108,6 +108,15 @@ The next step is to copy and commit these binaries to staging svnpubsub:: svn add cassandra-dist-dev/ svn ci cassandra-dist-dev/ +After committing the binaries to staging, increment the version number in Cassandra on the `cassandra-` + + cd ~/git/cassandra/ + git checkout cassandra- + edit build.xml # update ` ` + edit debian/changelog # add entry for new version + edit CHANGES.txt # add entry for new version + git commit -m "Update version to " build.xml debian/changelog CHANGES.txt + git push Call for a Vote ===============