Page "BloodhoundReleaseProcess" was changed by gjm Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=30> Revision 30 Comment: updating release process for post graduation Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: BloodhoundReleaseProcess ========================================================================= --- BloodhoundReleaseProcess (version: 29) +++ BloodhoundReleaseProcess (version: 30) @@ -9,7 +9,7 @@ 1. Check out the trunk of bloodhound. For example: {{{ #!sh -svn co https://svn.apache.org/repos/asf/incubator/bloodhound/trunk bh_trunk +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. Check http://ci.apache.org/projects/bloodhound/rat-output.html for any unapproved licences or missing license headers. @@ -19,11 +19,11 @@ 1. If this is a to be a new x.y release, create a new branch named <version number>: {{{ #!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" +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" }}} 1. Switch the working copy to the new branch. {{{#!sh -svn switch https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<version number> +svn switch https://svn.apache.org/repos/asf/bloodhound/branches/<version number> }}} 1. On the branch, for each {{{bloodhound_<package>/setup.cfg}}} file set: {{{ @@ -34,77 +34,72 @@ tag_svn_revision = false }}} Commit changes back to the branch. -1. Export branch to separate directory, named apache-bloodhound-incubating-<version number>: +1. Export branch to separate directory, named apache-bloodhound-<version number>: {{{ #!sh -svn export https://svn.apache.org/repos/asf/incubator/bloodhound/branches/<vesion number> apache-bloodhound-incubating-<version number> +svn export https://svn.apache.org/repos/asf/bloodhound/branches/<vesion number> apache-bloodhound-<version number> }}} 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-incubating-<version number>.tar.gz /path/to/directory +tar -pvczf apache-bloodhound-<version number>.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-incubating-<version number>.tar.gz.asc --detach-sig apache-bloodhound-incubating-<version number>.tar.gz +gpg --armor --output apache-bloodhound-<version number>.tar.gz.asc --detach-sig apache-bloodhound-<version number>.tar.gz }}} 1. Create an md5 file for the tar.gz file. For example with gpg: {{{ #!sh -gpg --print-md MD5 apache-bloodhound-incubating-<version number>.tar.gz > apache-bloodhound-incubating-<version number>.tar.gz.md5 +gpg --print-md MD5 apache-bloodhound-<version number>.tar.gz > apache-bloodhound-<version number>.tar.gz.md5 }}} 1. Checkout the `bloodhound-dist` directory, remove artifacts from previous releases and check in the changes. {{{ #!sh -svn co https://dist.apache.org/repos/dist/dev/incubator/bloodhound bloodhound_dist_dev -svn rm apache-bloodhound-incubating-* +svn co https://dist.apache.org/repos/dist/dev/bloodhound bloodhound_dist_dev +svn rm apache-bloodhound-* svn ci bloodhound_dist_dev -m "removing artifacts from previous release" }}} 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-incubating-<version number>.* bloodhound_dist_dev/ -svn add bloodhound_dist_dev/apache-bloodhound-incubating-<version number>* +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" }}} 1. Create a tag for the release {{{ #!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" +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" }}} 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. +1. Call for a vote on the [email protected] mailing list. You can use the [#InitialVoteTemplate initial call to vote template] below for this. 1. Wait at least 72 hours before announcing a result - 1. A minimum of three PPMC members need to vote +1 to succeed + 1. A minimum of three positive binding votes are required to succeed - currently binding votes are those given by Bloodhound committers. 1. On replying to announce the results, the subject of the email should be changed to [RESULT]. The [#InitialResultTemplate Initial result email template] can be used for this purpose. -1. If the bh-dev@ vote was successful, call for a vote on the general@ incubator mailing list including a summary of the PPMC vote. The summary can be in the form of a vote thread permalink which can be found from a search like [[http://markmail.org/search/?q=list%3Aorg.apache.incubator.bloodhound-dev+subject%3A%22[VOTE]+Release%22+order%3Adate-backward|this one on markmail.org]]. To ensure that the email does not retain a replyto set to the bh-dev list it may be better to compose a fresh email and the [#IncubatorVoteTemplate Incubator vote template] can be used to help write the message. - 1. Wait at least 72 hours before announcing a result - 1. A minimum of three IPMC members need to vote +1 to succeed -1. Again, on replying to announce the results, the subject of the email should be changed to [RESULT] 1. If the votes were successful, copy the release files to the release location: {{{ #!sh -svn co https://dist.apache.org/repos/dist/release/incubator/bloodhound bloodhound_dist_release +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-incubating-<version number>* +svn add bloodhound_dist_release/apache-bloodhound-<version number>* svn commit bloodhound_dist_release -m "releasing Bloodhound <version number>" }}} and wait for about 24 hours before moving on to announce the release (to give time for mirrors to update) '''[=#InitialVoteTemplate Initial call to vote template:]''' {{{ -To: [email protected] -Subject: [VOTE] Release Apache Bloodhound <version> (incubating) +To: [email protected] +Subject: [VOTE] Release Apache Bloodhound <version> }}} {{{ Hi everyone, -I would like to initiate the vote for releasing Apache Bloodhound <version number> -(incubating). +I would like to initiate the vote for releasing Apache Bloodhound <version number>. Please find the change log for this proposed release below: @@ -113,24 +108,23 @@ The release candidate artifacts consist of source release as a tar.gz archive along with the associated MD5 and GPG signature. These can be found at: -https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ +https://dist.apache.org/repos/dist/dev/bloodhound/ The archive is based on the tag: -http://svn.apache.org/viewvc/incubator/bloodhound/tags/<version number>-incubating +http://svn.apache.org/viewvc/bloodhound/tags/<version number> Please vote: [ ] +1 Release this package as Apache Bloodhound <version number> [ ] +0 Don't care [ ] -1 Do not release this package (please explain) -The vote is open for 72 hours and, if successful, will be followed by a -vote on general@incubator for a further 72 hours. +The vote is open for a minimum of 72 hours. }}} '''[=#InitialResultTemplate Initial result email template:]''' {{{ -To: [email protected] -Subject: [RESULT][VOTE] Release Apache Bloodhound <version> (incubating) +To: [email protected] +Subject: [RESULT][VOTE] Release Apache Bloodhound <version> }}} {{{ Hi, @@ -146,57 +140,21 @@ The vote therefore <passed|failed> with <sum of binding votes> binding votes. }}} -'''[=#IncubatorVoteTemplate Incubator vote template:]''' -{{{ -To: [email protected] -Cc: [email protected] -Subject: [VOTE] Release Apache Bloodhound <version> (incubating) -}}} -{{{ -Hi everyone, - -I would like to initiate the vote for releasing Apache Bloodhound <version number> -(incubating) in the incubator following the successful vote of the Bloodhound PPMC. - -The vote PPMC vote thread: - <vote thread perma-link> - -Please find the change log for this proposed release below: - -<Insert Release notes here> - -The release candidate artifacts consist of source release as a tar.gz -archive along with the associated MD5 and GPG signature. -These can be found at: -https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ - -The archive is based on the tag: -http://svn.apache.org/viewvc/incubator/bloodhound/tags/<version number>-incubating - -Please vote: -[ ] +1 Release this package as Apache Bloodhound <version number> -[ ] +0 Don't care -[ ] -1 Do not release this package (please explain) - -The vote is open for 72 hours. -}}} - === Announcing the release === 1. About 24 hours after moving the release artifacts to the release location, send an announcement email '''from your apache.org email account''' to ensure that mirrors are updated. The [#ReleaseAnnouncementTemplate Release announcement template] below can be used for the announcement. 1. Update other locations that mention a specific release: 1. https://issues.apache.org/bloodhound/wiki/WikiStart (Download link and text) - 1. http://incubator.apache.org/projects/bloodhound.html#News - edit: https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/bloodhound.xml - 1. http://incubator.apache.org/bloodhound/ - edit: https://svn.apache.org/repos/asf/incubator/bloodhound/site/index.html + 1. http://bloodhound.apache.org/ - edit: https://svn.apache.org/repos/asf/bloodhound/site/index.html '''[=#ReleaseAnnouncementTemplate Release announcement template:]''' {{{ -To: [email protected], [email protected], [email protected] -Cc: [email protected] -Subject: [ANNOUNCE] Apache Bloodhound <version> incubating Released +To: [email protected], [email protected] +Cc: [email protected] +Subject: [ANNOUNCE] Apache Bloodhound <version> Released }}} {{{ -The Apache Bloodhound (Incubating) team is pleased to announce the availability -of the <version>-incubating release. +The Apache Bloodhound team is pleased to announce the availability +of the <version> release. Apache Bloodhound is a tool to track progress and defects in software products. @@ -210,20 +168,10 @@ In this release we [USE THIS PARAGRAPH TO NOTE SOME INTERESTING CHANGES] The release can be downloaded from: - http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-<version>.tar.gz + http://www.apache.org/dyn/closer.cgi/bloodhound/apache-bloodhound-<version>.tar.gz For further information, please visit the project website at - http://incubator.apache.org/bloodhound/ + http://bloodhound.apache.org/ The Apache Bloodhound Team - -Disclaimer: -Apache Bloodhound is an effort undergoing incubation at The Apache Software -Foundation (ASF), sponsored by the Apache Incubator. Incubation is required -of all newly accepted projects until a further review indicates that the -infrastructure, communications, and decision making process have stabilized -in a manner consistent with other successful ASF projects. While incubation -status is not necessarily a reflection of the completeness or stability of -the code, it does indicate that the project has yet to be fully endorsed by -the ASF. }}} -------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 .
