natas_hw
/
cassandra
mirror of https://github.com/apache/cassandra
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Mick Semb Wever 2019-09-21 18:53:14 +02:00
parent f9ff884377
commit b0f9d72840
No known key found for this signature in database
GPG Key ID: E91335D77E3E87CB
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/development/release_process.rst
View File

@ -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
===============