You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/07/09 01:10:35 UTC

[Apache Bloodhound] BloodhoundReleaseProcess modified

Page "BloodhoundReleaseProcess" was changed by rjollos
Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=34>
Revision 34
Comment: Only need to search for tickets with Resolution=fixed.
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundReleaseProcess
=========================================================================
--- BloodhoundReleaseProcess (version: 33)
+++ BloodhoundReleaseProcess (version: 34)
@@ -11,7 +11,7 @@
 #!sh
 svn co https://svn.apache.org/repos/asf/bloodhound/trunk bh_trunk
 }}}
-  1. Review the tickets that have been resolved since the last release, and update the RELEASE_NOTES file highlighting new features and issues fixed, optionally including major known issues that remain. The relevant tickets will usually be associated with a single milestone. However, check for tickets that are part of this release but have been closed [/query?status=closed&milestone=&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority without the milestone set].
+  1. Review the tickets that have been resolved since the last release, and update the RELEASE_NOTES file highlighting new features and issues fixed, optionally including major known issues that remain. The relevant tickets will usually be associated with a single milestone. However, check for tickets that are part of this release but have been closed [query:status=closed&resolution=fixed&milestone= without the milestone set].
   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 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.
-------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 .