...
- If you have not already done so, append your code signing key to the KEYS file. Once you commit your changes, they will automatically be propagated to the website. Also upload your key to a public key server if you haven't. End users use the KEYS file (along with the web of trust) to validate that releases were done by an Apache committer. For more details on signing releases, see Signing Releases and Step-By-Step Guide to Mirroring Releases.
- Make sure to update the various LICENSE and NOTICE files per Apache policy.
- Bulk update JIRA to unassign from this release all issues that are open non-blockers.
- Send follow-up notification to the developer list that this was done.
- To deploy artifacts to the Apache Maven repository create
~/.m2/settings.xml
:
Code Block |
---|
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
...
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
...
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
|
...
http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
...
<servers> |
...
<server> |
...
...
<id>apache.staging.https</id> |
...
<username>Apache username</username> |
...
<password>Apache password</password> |
...
</server> |
...
</servers>
</settings> |
Branching
When releasing Hadoop X.Y.Z, the following branching changes are required. Note that a release can match more than one of the following if-conditions. For a major release, one needs to make the changes for minor and point releases as well. Similarly, a new minor release is also a new point release.
...