This document describes how to make a release of Sqoop. It is a work in progress and should be refined by the Release Manager (RM) as they come across aspects of the release process not yet documented here.
NOTE: For the purpose of illustration, this document assumes that the version being released is 1.4.3, and the following development version will become 1.4.4.
- Creating Release Artifacts
- Running the vote
- Rolling out the Release
- Upload the artifacts
- Wait for 24 Hours
- Announce the release
- Publish binary artifacts in Maven Repository
- Updating the website and the wiki with the new Sqoop bits:
Frequently asked questions for making Apache releases are available on Releases FAQ page.
The Release Manager (RM) must go through the policy document to understand all the tasks and responsibilities of running a release.
The RM should first create an umbrella issue and then setup a timeline for release branch point. The time for the day the umbrella issue is created to the release branch point must be at least two weeks in order to give the community a chance to prioritize and commit any last minute features and issues they would like to see in the upcoming release.
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.
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:
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 '1.4.3'.
You can also run the following query to make sure that the issues fixed for the to-be-released version look accurate:
It is important that between the time that the umbrella issue is filed to the time when the release branch is created, no experimental or potentially destabilizing work is checked into the trunk. While it is acceptable to introduce major changes, they must be thoroughly reviewed and have good test coverage to ensure that the release branch does not start of being unstable.
If necessary the RM can discuss if certain issues should be fixed on the trunk in this time, and if so what is the gating criteria for accepting them.
1. Send an email to email@example.com to
- Notify that you are about to branch.
- Ask to hold off any commits until this is finished.
2. Send another email after branching is done.
1. Checkout the trunk.
2. Update CHANGELOG.txt in the trunk.
- For example,
3. Build source release and check that all included libraries are mentioned in the LICENSE.txt file. If not then update this file and commit your changes.
4. Update the "version" value of build.xml in trunk to "1.4.3".
5. Commit back to the trunk.
6. Create a branch.
7. Update the "oldversion" value of build.xml in the trunk to "1.4.3".
8. Update the "version" value of build.xml in the trunk to "1.4.4-SNAPSHOT".
9. Commit back to the trunk.
10. Tag a candidate, where R (starting from 0) is the iteration number for this candidate:
1. Check out the candidate.
2. Make sure that LICENSE.txt contains license information for all third-party libraries and codes to be included in source tarball. You can overwrite with LICENSE.txt from source tarball of previous release if there is no change.
3. Generate the source tarball
4. Copy generated tarball to some temporary location
5. Make sure that LICENSE.txt contains license information for all third-party libraries and codes to be included in binary tarball. You can overwrite with LICENSE.txt from binary tarball of previous release if there is no change.
6. Execute steps 7-8 for each supported binary version (20, 23, 100, 200)
7. Generate the binary tarball
8. Copy generated tarball to some temporary location
9. Alternatively instead of steps 6-8 you can execute following shell command
1. Unpack the source tarball
2. Run tests.
3. Check license header
4. Do the same for the binary tarball.
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:
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:
This will take some time to propagate in which you can continue with the other steps of the release process.
For every release artifact, there should be a corresponding signature file (*.asc) that can be generated using PGP as follows:
The above command will generate the new file
sqoop-1.4.2.tar.gz.asc which contains the signature that can be verified using the following command:
The md5sum allows a user to ensure that the bits they have downloaded are consistent and same as what were produced during the release. You must create md5sum for every artifact that is being released. Use the following command to generate the md5sum:
In order to allow other developers and contributors to verify the release artifacts, you need to stage them in a place that is accessible to them to download it from. It is preferred if you post these artifacts on your own web-space on people.apache.org. Please make sure that you post all the release artifacts, their signature files (.asc) and their md5 (.md5) files.
Send an email to dev@ list. For example,
Need 3 +1 votes from PMC members.
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.
It may take up to 24 hours for all mirrors to sync up.
Send an email to firstname.lastname@example.org (the from: address must be @apache.org). For example,
Sqoop already has a Nexus repository setup, thanks to INFRA-4310. The following steps outline how you can publish Sqoop binaries to this repository.
As we now need to deploy artifacts compiled against various hadoop distributions, we've moved the classifier from "test" to "hadoop
". You will need to set up the maven as is instructed in official guide.
Follow the details provided in Maven Password Encryption Guide to set up a master password for your system.
Once the master password has been created, update your maven settings file (~/.m2/settings.xml) to have the following server entries:
In a newly created directory, checkout the sources from the appropriate release tag location. For example, for the release 1.4.0-incubating the sources will need to be checked out from
https://svn.apache.org/repos/asf/incubator/sqoop/tags/release-1.4.0-rc1/. Once you have the sources, build them to generate the binaries. For example:
Before you do this step, remove any previously installed Sqoop artifacts from your local maven cache. You can do this by running the following command:
Now run the following command to install the newly checked-out and built artifacts of Sqoop from the previous step to your local maven cache.
This will result in copying of the built artifacts and generated POM file into your local maven cache.
Once the artifacts are in your local cache, you can now deploy them to Nexus staging repository.
Start out by going into the directory where the main artifact is generated. Once there, make sure that the generated POM file looks accurate and if not, fix it manually. Then run the following commands to deploy the main artifact.
This will result in the signing and deployment of the main artifact
sqoop-1.4.0-incubating.jar in this case, to the staging repository. If all goes well you should be able to point your browser to Apache Nexus Repository and clicking on the Staging Repository link on the left navigation column. When you select the staging repository in the right pane, the pane will split into a content pane below that shows how the content of the staging repository created by the above command. The following screenshot illustrates what this looks like.
To deploy the test artifact to the staging repo, you must copy the generated test artifact to the same directory as that of the main directory so that you can use the main artifact POM and specify a classifier. Here are the commands to do that:
If this command succeeds, you can now see the test artifacts deployed in the staging repository as well. Go the the browser and click on the refresh button on the content area to reload the contents of the staging repository. The following screen shot is an example of how the staging repository may look like after these steps.
In the Nexus main content pane, make sure the staging repository you are working with is selected with a check mark, and click the "Close" button on top. This causes Nexus to verify the signatures and if everything is valid, it will result in successful closing of the repository. If there are any failures due to invalid signatures, you will have to drop the repository and redo the steps outlined in this section again.
Once the repository is closed, you can promote it to release status by clicking on the "Release" button on top. This allows the artifacts in this staging repository to be published to release repository immediately. Once the release has propagated, you should receive a confirmation email from Nexus stating that the artifacts are now available in the release repository.