THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
NOTE: For the purpose of illustration, this document assumes that the version being released is 1.99.1, and the following development version will become 1.99.2
...
| Table of Contents | ||
|---|---|---|
|
...
Prerequisites
...
Policy documents
...
The RM should then send the pointer to the umbrella issue along with the tentative timeline for branch point to the user and developer lists. Any work identified as release related that needs to be completed should be added as a subtask of the umbrella issue to allow users to see the overall release progress in one place.
| No Format |
|---|
To: dev@sqoop.apache.org
Subject: Work on $release release has started
We are starting the process to prepare for Sqoop $release release. I have opened JIRA $jira to cover the tasks under this release.
If you have any JIRA in progress and would like to include it in this release, please follow the process to do so.
Feel free to comment on the JIRA if you have any comments/suggestions.
Thanks,
$RM
|
...
Before a release is done, make sure that any issues that are fixed have their fix version setup correctly. Run the following JIRA query to see which resolved issues do not have their fix version set up correctly:
| Code Block |
|---|
project = sqoop and resolution = fixed and fixVersion is empty
|
...
You can also run the following query to make sure that the issues fixed for the to-be-released version look accurate:
| Code Block |
|---|
project = sqoop and resolution = fixed and fixVersion = '1.99.1'
|
...
1. Clone fresh repository copy
| Code Block |
|---|
git clone https://git-wip-us.apache.org/repos/asf/sqoop.git
cd sqoop
|
2. Checkout Sqoop 2 branch
| Code Block |
|---|
git checkout sqoop2
|
3. Check that current HEAD points to commit on which you want to base new release branch. Checkout particular commit if not.
| Code Block |
|---|
git log # Check current branch history. HEAD should point to commit that you want to be base for your release branch
git checkout abcdef123 # Check out particular commit that should be base for release branch if -^
|
4. Create new release branch with name "branch-$version"
| Code Block |
|---|
git branch branch-1.99.1
|
5. Push new branch to Apache repository
| Code Block |
|---|
git push origin branch-1.99.1
|
...
8. Check your changes by running package build
| Code Block |
|---|
mvn package
|
9. Commit your changes and push them to Apache repository
| Code Block |
|---|
git commit -a -m "Changing version to 1.99.1"
git push origin branch-1.99.1
|
...
2. You can use ruby script jira2changelog.rb attached to this page to transform this page into desired output.
| Code Block |
|---|
jira2changelog.rb 'https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311320&version=12323641' # Change with your version Release notes
|
...
1. Check out release branch
| Code Block |
|---|
git clone https://git-wip-us.apache.org/repos/asf/sqoop.git
git checkout branch-1.99.1
|
2. Make sure that LICENSE.txt contains license information for all third-party libraries. In order to do this check properly, you will need to quickly create all packages. You need to check jars available in client/lib, server/lib and insider sqoop server war file (server/webapps/sqoop.war).
| Code Block |
|---|
mvn package -DskipTest
mvn package -DskipTests -Pbinary -Dhadoop.profile=100
mvn package -DskipTests -Pbinary -Dhadoop.profile=200
|
2. Create tag on this commit to identify precise point where the RC was generated and push this tag to main repository
| Code Block |
|---|
git tag -a release-1.99.1-rc0 -m "Sqoop 1.99.1-rc0 release"
git push origin release-1.99.1-rc0
|
3. Create temporary directory where you'll be preparing all required artifacts
| Code Block |
|---|
mkdir -p /tmp/sqoop-release-preparations
|
4. Create source artifact and move it to your temporary directory
| Code Block |
|---|
mvn clean verify package
mv dist/target/sqoop-1.99.1.tar.gz /tmp/sqoop-release-preparations
|
5. Create binary artifact for each supported hadoop version and move generated artifacts to your temporary directory
| Code Block |
|---|
for version in 200 100; do mvn clean verify package -Pbinary -Dhadoop.profile=$version; mv dist/target/sqoop-1.99.1-bin-hadoop${version}.tar.gz /tmp/sqoop-release-preparations ; done
|
...
If your PGP key is not yet in the project's KEYS file, you need to first add that in. To do this, checkout the KEYS file and update it using the following commands:
| Code Block |
|---|
$ svn co https://svndist.apache.org/repos/asfdist/release/sqoop/dist sqoop-distrelease ... $ cd sqoop-distrelease $ (gpg --list-sigs <KEY-ID> && gpg --armor --export <KEY-ID> ) >> KEYS $ svn commit -m "Adding PGP public key to KEYS file" KEYS ... |
Once this file has been updated, you need to publish it in the appropriate dist directory for the project on http://www.apache.org/dist/sqoop/KEYS. To do this, you must copy the file as follows:
| Code Block |
|---|
$ scp KEYS people.apache.org:/www/www.apache.org/dist/sqoop/KEYS
|
...
1. Change your working directory to the temporal one
| Code Block |
|---|
cd /tmp/sqoop-release-preparations
|
2. Sing each file with your key
| Code Block |
|---|
for file in *.tar.gz; do gpg --armor --output $file.asc --detach-sig $file; done
|
3. You can immediately verify your signature
| Code Block |
|---|
for file in *.tar.gz; do gpg --verify $file.asc $file; done
|
4. Create md5 check sum
| Code Block |
|---|
for file in *.tar.gz; do md5sum $file > $file.md5; done
|
5. Create sha1 check sum
| Code Block |
|---|
for file in *.tar.gz; do sha1sum $file > $file.sha; done
|
...
6. Upload artifacts and all created check sums with signatures to your own web-space on people.apache.org
| Code Block |
|---|
ssh people.apache.org "mkdir -p ~~/public_html/sqoop-1.99.1-rc0" scp * people.apache.org:~/public_html/sqoop-1.99.1-rc0 |
...
Send an email to dev@ list. For example,
| No Format |
|---|
To: dev@sqoop.apache.org
Subject: [VOTE] Release Sqoop version 1.99.1
This is the first cut of Sqoop 2 branch, version 1.99.1. Purpose of this release is to provide early bits to our users so that they can test the product and provide early feedback.This is the first cut of Sqoop 2 branch, version 1.99.1. Purpose of this release is to provide early bits to our users so that they can test the product and provide early feedback.
*** Please cast your vote by Friday 2012-12-21 ***
The list of fixed issues:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=blob;f=CHANGELOG.txt;h=c22af4131a3061dc78922a82a68eedc7e9ac599e;hb=85a8e1a8b3445360d66c8f812947cb0a7e8230c9
The tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
http://people.apache.org/~jarcec/sqoop-1.99.1-rc0/
The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git;a=tag;h=refs/tags/release-1.99.1-rc0
The KEYS file:
http://www.apache.org/dist/sqoop/KEYS
|
...
You can close the vote after voting period expires when you accumulate sufficient votes. Example close email:
| No Format |
|---|
To: dev@sqoop.apache.org
Subject: [CLOSED] [VOTE] Release Sqoop version 1.99.1
Thanks everyone for voting for this release, I'm closing the vote now. I'll send the results shortly.Thanks everyone for voting for this release, I'm closing the vote now. I'll send the results shortly.
$RM
|
After closing the vote, you need to send results. Example email:
| No Format |
|---|
To: dev@sqoop.apache.org
Subject: [RESULTS] [VOTE] Release Sqoop version 1.99.1
This vote passes with 8 +1 votes (4 bindings) and no 0 or -1 votes.
+1 votes
PMC Members:
* Bilung Lee
* Olivier Lamy
* Arvind Prabhakar
* Jarek Jarcec Cecho
Committers:
* Cheolsoo Park
* Abhijeet Gaikwad
Community:
* Hari Shreedharan
* Venkatesan Ranganathan
0 votes
* No votes
-1 votes
* No votes
Vote thread:
http://markmail.org/message/faioizetvcils2zo
I'll continue in the release process.
Jarcec
|
...
Sqoop is using SVN based release procedure. In order to release you have to checkout release repository located on https://dist.apache.org/repos/dist/release/sqoop and add release artifacts there.
| No Format |
|---|
svn co https://dist.apache.org/repos/dist/release/sqoop sqoop-release
cd sqoop-release
mkdir 1.99.1
cp $source_to_your_artifacts 1.99.1/
svn add 1.99.1
# Optionally change KEYS file in case that you've added your key for the first time
svn commit -m "Release 1.99.1"
|
...
Send an email to announce@apache.org (the from: address must be @apache.org). For example,
| No Format |
|---|
To: announce@apache.org, user@sqoop.apache.org, dev@sqoop.apache.org
Subject: [ANNOUNCE] Apache Sqoop 1.99.1 released
The Apache Sqoop team is pleased to announce the release of Sqoop 1.99.1.
This is the first cut of Sqoop2 branch. Major step forward of the project.
Apache Sqoop is 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/sqoop/1.99.1
The full change log is available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311320&version=12323641
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://sqoop.apache.org/.
The Apache Sqoop Team
|
...
1. Configure your Apache credentials in your maven settings.xml file (usually in ~/.m2/settings.xml). More information is available in official guide.
| Code Block |
|---|
<servers>
<server>
<id>apache.releases.https</id>
<username>APACHE-ID</username>
<password>APACHE-PASSWORD</password>
</server>
</servers>
|
...
3. Create, sign and deploy artifacts into staging repository
| Code Block |
|---|
for version in 100 200; do mvn clean deploy -Psign -Dhadoop.profile=$version ; done
|
...