incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject [Apache Bloodhound] BloodhoundReleaseProcess modified
Date Fri, 11 Jan 2013 18:17:26 GMT
Page "BloodhoundReleaseProcess" was changed by gjm
Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=4>
Revision 4
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundReleaseProcess
=========================================================================
--- BloodhoundReleaseProcess (version: 3)
+++ BloodhoundReleaseProcess (version: 4)
@@ -2,15 +2,24 @@
 
 === Prerequisites ===
 1. Commit access to {{{svn.apache.org/[...]bloodhound}}} and {{{dist.apache.org}}}
-1. PGP registered on the Apache ID
+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
 
 === 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. Create branch named <version number>
-1. Export branch to separate directory, named apache-bloodhound-incubating-<version number>
+ 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>:
+{{{
+svn copy https://svn.apache.org/repos/asf/incubator/bloodhound/trunk https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<version
number> -m "branching for new release"
+}}}
+After this point, if there are any issues that block release, fixes should be 
+1. Export branch to separate directory, named apache-bloodhound-incubating-<version number>:
+{{{
+ 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:
 {{{
@@ -18,7 +27,7 @@
 }}}
 1. Create a detached signature file for the tar.gz file. For example, on the command line
with gpg:
 {{{
-gpg --armor --output apache-bloodhound-incubating-<version number>.tar.gz.asx --detach-sig
apache-bloodhound-incubating-<version number>.tar.gz
+gpg --armor --output apache-bloodhound-incubating-<version number>.tar.gz.asc --detach-sig
apache-bloodhound-incubating-<version number>.tar.gz
 }}}
 1. Create an md5 file for the tar.gz file. For example with gpg:
 {{{
-------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 .

Mime
View raw message