This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new b0f9d72 Add the how and when to perform the step of incrementing the
codebase's version into the existing release process documentation
b0f9d72 is described below
commit b0f9d72840ec13030ad97ad77bf7478a079c2f6f
Author: Mick Semb Wever <[email protected]>
AuthorDate: Sat Sep 21 18:53:14 2019 +0200
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 b3c4032..0ab6dff 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/<version>
svn ci cassandra-dist-dev/<version>
+After committing the binaries to staging, increment the version number in
Cassandra on the `cassandra-<version-branch>`
+
+ cd ~/git/cassandra/
+ git checkout cassandra-<version-branch>
+ edit build.xml # update `<property name="base.version"
value="…"/> `
+ edit debian/changelog # add entry for new version
+ edit CHANGES.txt # add entry for new version
+ git commit -m "Update version to <next-version>" build.xml
debian/changelog CHANGES.txt
+ git push
Call for a Vote
===============
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
