Page "BloodhoundReleaseProcess" was changed by rjollos Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=47> Revision 47 Comment: Use a shell variable so that commands can be copy-pasted. Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: BloodhoundReleaseProcess ========================================================================= --- BloodhoundReleaseProcess (version: 46) +++ BloodhoundReleaseProcess (version: 47) @@ -16,13 +16,16 @@ 1. Update NOTICE and LICENSE files if required (should any licenses be added/removed; are the locations specified still accurate). 1. Update packages version numbers in {{{bloodhound_<package>/setup.py}}} files to reflect the current overall version number (if required). The package version numbers should have been updated at the start of the release cycle. 1. Commit changes back to trunk. -1. If this is a to be a new x.y release, create a new branch named <version number>: +1. If this is a to be a new x.y release, create a new branch named <version number>. Set a variable in the shell in order to copy and paste the commands that follow: {{{#!sh -svn copy https://svn.apache.org/repos/asf/bloodhound/trunk https://svn.apache.org/repos/asf/bloodhound/branches/<version number> -m "branching for new release" +VER=<version number> +}}} +{{{#!sh +svn copy https://svn.apache.org/repos/asf/bloodhound/trunk https://svn.apache.org/repos/asf/bloodhound/branches/$VER -m "branching for new release" }}} 1. Switch the working copy to the new branch. {{{#!sh -svn switch https://svn.apache.org/repos/asf/bloodhound/branches/<version number> +svn switch https://svn.apache.org/repos/asf/bloodhound/branches/$VER }}} 1. On the branch, for each {{{bloodhound_<package>/setup.cfg}}} file set: {{{#!ini @@ -32,26 +35,26 @@ tag_svn_revision = false }}} Commit changes back to the branch. -1. Export branch to separate directory, named apache-bloodhound-<version number>: +1. Export branch to separate directory, named apache-bloodhound-$VER: {{{#!sh -svn export https://svn.apache.org/repos/asf/bloodhound/branches/<version number> apache-bloodhound-<version number> +svn export https://svn.apache.org/repos/asf/bloodhound/branches/$VER apache-bloodhound-$VER }}} 1. Check for open tickets requiring the exclusion of files and directories for the current release and remove them. 1. Create a tar.gz of that directory: {{{#!sh -tar -pvczf apache-bloodhound-<version number>.tar.gz /path/to/directory +tar -pvczf apache-bloodhound-$VER.tar.gz /path/to/directory }}} 1. Create a detached signature file for the tar.gz file. For example, on the command line with gpg: {{{#!sh -gpg --armor --output apache-bloodhound-<version number>.tar.gz.asc --detach-sig apache-bloodhound-<version number>.tar.gz +gpg --armor --output apache-bloodhound-$VER.tar.gz.asc --detach-sig apache-bloodhound-$VER.tar.gz }}} 1. You may want to verify the signature, particularly if this is the first time you are signing a release with this key. Look for //Good signature// in the output: {{{#!sh -$ gpg --verify apache-bloodhound-<version number>.tar.gz.asc apache-bloodhound-<version number>.tar.gz +$ gpg --verify apache-bloodhound-$VER.tar.gz.asc apache-bloodhound-$VER.tar.gz }}} 1. Create an md5 file for the tar.gz file. For example with gpg: {{{#!sh -gpg --print-md MD5 apache-bloodhound-<version number>.tar.gz > apache-bloodhound-<version number>.tar.gz.md5 +gpg --print-md MD5 apache-bloodhound-$VER.tar.gz > apache-bloodhound-$VER.tar.gz.md5 }}} 1. Checkout the `bloodhound-dist` directory, remove artifacts from previous releases and check in the changes. {{{#!sh @@ -61,13 +64,13 @@ }}} 1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files [release files] to the `bloodhound-dist` directory. Add your PGP key to the `KEYS` file in this directory if it has not been previously added. {{{#!sh -cp apache-bloodhound-<version number>.* bloodhound_dist_dev/ -svn add bloodhound_dist_dev/apache-bloodhound-<version number>* -svn commit bloodhound_dist_dev -m "adding <version number> artifacts to the Bloodhound dist/dev area for release votes" +cp apache-bloodhound-$VER.* bloodhound_dist_dev/ +svn add bloodhound_dist_dev/apache-bloodhound-$VER* +svn commit bloodhound_dist_dev -m "adding $VER artifacts to the Bloodhound dist/dev area for release votes" }}} 1. Create a tag for the release {{{#!sh -svn copy https://svn.apache.org/repos/asf/bloodhound/branches/<version number> https://svn.apache.org/repos/asf/bloodhound/tags/<version number> -m "tagging release" +svn copy https://svn.apache.org/repos/asf/bloodhound/branches/$VER https://svn.apache.org/repos/asf/bloodhound/tags/$VER -m "tagging release" }}} 1. On the trunk, update the packages version numbers in {{{bloodhound_<package>/setup.py}}} files to the next development version. Commit changes back to the trunk. @@ -81,7 +84,7 @@ svn co https://dist.apache.org/repos/dist/release/bloodhound bloodhound_dist_release cp bloodhound_dist_dev/* bloodhound_dist_release/ svn add bloodhound_dist_release/apache-bloodhound-<version number>* -svn commit bloodhound_dist_release -m "releasing Bloodhound <version number>" +svn commit bloodhound_dist_release -m "releasing Bloodhound $VER" }}} and wait for about 24 hours before moving on to announce the release (to give time for mirrors to update) -------8<------8<------8<------8<------8<------8<------8<------8<--------
-- Page URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'BloodhoundReleaseProcess' page. If it was not you, please report to .
