THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
TODO: Add an email template to send out
...
JIRA cleanup
Before a release is done, make sure that any issues that are fixed have their fix version fixVersion setup correctly. Run the following JIRA query to see which resolved issues do not have their fix version set up correctly:
| No Format |
|---|
project = flumeFlume and resolutionResolution = fixedFixed and fixVersion is emptyEMPTY |
The result of the above query should be empty. If some issues do show up in this query that have been fixed since the last release, please bulk-edit them to set the fix version to the version being released.
Since the JIRA release note tool will pull in list all JIRAs associated with a particular fixVersion , regardless of their Resolution, you may want to remove fixVersion on issues declared as "Duplicate", "Won't Fix", "Works As Expected", etc. You can use this query to find those issues, then just bulk edit them and leave the fixVersion field blank when editing them. (Note that you will need to replace "v1.0.0" below with the version you are trying to release.)
| No Format |
|---|
Projectproject = Flume and StatusResolution != Unresolved AND Resolution != fixedFixed AND fixVersion is empty= "v1.0.0" |
Finally, look at check out the output of the JIRA release note tool to see which JIRAs are included in the release, in order to do a sanity check.
...
Communicate with the community
1. Send an email to flume-dev@incubatordev@flume.apache.org to
Notify that you are about to branch.
Ask to hold off any commits until this is finished.
...
2. Update CHANGELOG in the trunk to indicate the changes going into the new version.
The change list can be gotten swiped from the JIRA release note tool (use the "text" format for the change log). See JIRA Cleanup above for how to sanitize this listto ensure that the release notes generated by this tool are what you are expecting.
3. Update the "version" value of all pom.xml in trunk to "1.0.0".
...
2. Generate a tarball.
| Code Block |
|---|
mvn -DskipTestsclean packageinstall |
3. Unpack the source tarball
| Code Block |
|---|
cd flume-ng-dist/target tar xvfxzvf apache-flume-1.0.0-src.tar.gz |
3. Run tests.4. Do another full build inside the source tarball
| Code Block |
|---|
mvn test
|
4. Check license header
| Code Block |
|---|
mvn verifyclean install |
Running the vote
Call for dev list votes
Send an email to flume-dev@ dev@flume.apache.org list. For example,
| No Format |
|---|
To: flume-dev@incubator.apache.org Subject: VOTE Release Apache flumeFlume version 1.0.0 This is the first incubator release for Apache flume, version 1.0.0. Please cast your vote by *** 3 working days after sending *** The list of fixed issues:http://svn.apache.org/repos/asf/incubator/flume/branches/branch-1.0.0/CHANGES.txtCHANGELOG The tarball (.tar.gz), signature (.asc), checksum (*.md5), license audit result (log/.ant_releaseaudit.log), and test result (log/.ant_test.log):http://people.apache.org/~prasadm/flume-1.0.0-rc0/ The tag to be voted upon:http://svn.apache.org/repos/asf/incubator/flume/tags/release-1.0.0-rc0 The KEYS http://www.apache.org/dist/incubator/flume/KEYS" |
Need You need 3 +1 votes from PPMC PMC members .
Call for incubator general list votes
Send an email to incubator-general@ list. For example,
| No Format |
|---|
To: general@incubator.apache.org
Subject: VOTE Release flume version 1.0.0
This is the first incubator release for Apache flume, version 1.0.0.
Please cast your vote by *** 3 working days after sending ***
Dev list vote thread:http://markmail.org/message/jehsoo2vi6xboovu
The list of fixed issues:http://svn.apache.org/repos/asf/incubator/flume/branches/branch-1.0.0/CHANGES.txt
The tarball (.tar.gz), signature (.asc), checksum (*.md5), license audit result
(log/.ant_releaseaudit.log), and test result (log/.ant_test.log):http://people.apache.org/~prasadm/flume-1.0.0-rc0/
The tag to be voted upon:http://svn.apache.org/repos/asf/incubator/flume/tags/release-1.0.0-rc0
The KEYS http://www.apache.org/dist/incubator/flume/KEYS"
|
Need 3 +1 votes from IPMC membersfor a release.
Rolling out the Release
Upload the artifacts
Source and convenience artifacts
| Code Block |
|---|
ssh people.apache.org cp -r ~/public_html/flume-1.0.0-rc0 /www/www.apache.org/dist/incubator/flume/flume-1.0.0 cd /www/www.apache.org/dist/incubator/flume chgrp -R incubator flume-1.0.0 chmod -R g+w flume-1.0.0 rm stable ln -s flume-1.0.0 stable rm r /www/www.apache.org/dist/incubator/flume/flume$PREVIOUS_VERSION # remove older versions |
It may take up to 24 hours for all mirrors to sync up.
Deploy Maven artifacts
TBD
Announce the release
Send an email to announce@apache.org (the from: address must be @apache.org). For example,
| No Format |
|---|
To: announce@apache.org, flume-user@incubator.apache.org, flume-dev@incubator.apache.org Subject: ANNOUNCE Apache flumeFlume 1.0.0 released The Apache flumeFlume team is pleased to announce the release of flumeFlume 1.0.0 from the Apache Incubator. This is the first incubator release of Apache flume, a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores, such as relational databases. The release is available here:http://www.apache.org/dyn/closer.cgi/incubator/flume/ The full change log is available here:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311320&version=12317345 Your help and feedback is more than welcome. For more information on how to report problems and to get involved, visit the project website at http://incubator.apache.org/flume/. The Apache flumeFlume Team |