Page "BloodhoundReleaseProcess" was changed by rjollos
Diff URL: 
<https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=27>
Revision 27
Comment: Minor changes while preparing release 0.5.
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundReleaseProcess
=========================================================================
--- BloodhoundReleaseProcess (version: 26)
+++ BloodhoundReleaseProcess (version: 27)
@@ -13,7 +13,7 @@
 }}}
   1. Update the RELEASE_NOTES file highlighting new features and issues fixed, 
optionally including major known issues that remain
   1. Check http://ci.apache.org/projects/bloodhound/rat-output.html for any 
unapproved licences or missing license headers.
-  1. Update NOTICE and LICENSE files if required (should any licenses be 
added/removed; are the locations specified still accurate)
+  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>:
@@ -21,19 +21,25 @@
 #!sh
 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"
 }}}
+1. Switch the working copy to the new branch.
+{{{#!sh
+svn switch 
https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<version number>
+}}}
 1. On the branch, for each {{{bloodhound_<package>/setup.cfg}}} file set:
  {{{
  #!ini
+ [egg_info]
  tag_build =
+ tag_date = 0
  tag_svn_revision = false
  }}}
- Verify that the version strings are displayed in the ''Installed Plugins'' 
section of the `/about` page without the `dev` string and an SVN revision 
appended (e.g. `0.5.0` rather than `0.5.0dev-r12345`). Commit changes back to 
the branch.
+ Commit changes back to the branch.
 1. Export branch to separate directory, named 
apache-bloodhound-incubating-<version number>:
 {{{
 #!sh
 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. 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
@@ -49,7 +55,7 @@
 #!sh
 gpg --print-md MD5 apache-bloodhound-incubating-<version number>.tar.gz > 
apache-bloodhound-incubating-<version number>.tar.gz.md5
 }}}
-1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files 
[release files] to the 
{{{https://dist.apache.org/repos/dist/dev/incubator/bloodhound}}} directory. 
Add your PGP key to the `KEYS` file in this directory if it has not been 
previously added.
+1. Checkout and 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
 svn co https://dist.apache.org/repos/dist/dev/incubator/bloodhound 
bloodhound_dist_dev
@@ -62,7 +68,7 @@
 #!sh
 svn copy 
https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<version number> 
https://svn.apache.org/repos/asf/incubator/bloodhound/tags/<version 
number>-incubating -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.
+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.
 
 === Voting process ===
 1. Call for a vote on the bh-dev@ mailing list. You can use the 
[#InitialVoteTemplate initial call to vote template] below for this.
-------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 .

Reply via email to