Page "BloodhoundReleaseProcess" was changed by gjm Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=17> Revision 17 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: BloodhoundReleaseProcess ========================================================================= --- BloodhoundReleaseProcess (version: 16) +++ BloodhoundReleaseProcess (version: 17) @@ -1,16 +1,20 @@ = Bloodhound Release Process = === Prerequisites === -1. Commit access to {{{svn.apache.org/[...]bloodhound}}} and {{{dist.apache.org}}} -1. PGP code signing key uploaded to a public keyserver and added to your account details at https://id.apache.org the Apache ID. Details here: http://www.apache.org/dev/openpgp.html#generate-key +1. Commit access to {{{svn.apache.org}}} and {{{dist.apache.org}}} repositories (in particular the bloodhound parts of these referred to below) +1. PGP code signing key uploaded to a public keyserver and added to your account details at https://id.apache.org. Details for creating such a key can be found here: http://www.apache.org/dev/openpgp.html#generate-key === Prepare the release === -1. Update the RELEASE_NOTES file highlighting new features and issues fixed - 1. Optionally include major known issues that remain - 1. Update NOTICES file if required - 1. Check http://ci.apache.org/projects/bloodhound/rat-output.html for any unapproved licences or missing license headers - 1. Update packages version numbers to reflect the current overall version number if required - 1. Commit changes back to trunk. +1. Update files in trunk to reflect the current status: + 1. Check out the trunk of bloodhound. For example: +{{{ +#!sh +svn co https://svn.apache.org/repos/asf/incubator/bloodhound/trunk bh_trunk +}}} + 1. Update the RELEASE_NOTES file highlighting new features and issues fixed, optionally including major known issues that remain + 1. Update NOTICES file if required, checking http://ci.apache.org/projects/bloodhound/rat-output.html for any unapproved licences or missing license headers + 1. Update packages version numbers in {{{bloodhound_<package>/setup.py}}} files to reflect the current overall version number if required + 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>: {{{ #!sh @@ -22,7 +26,7 @@ svn export https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<vesion number> apache-bloodhound-incubating-<version number> }}} 1. Check for open tickets requiring the exclusion of files and directories for the current release and remove these -1. Zip up that directory in Terminal (OS X 10.8) using: +1. Create a tar.gz of that directory: {{{ #!sh tar -pvczf apache-bloodhound-incubating-<version number>.tar.gz /path/to/directory -------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 (incubating) 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 .
