...

1. 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.
2. Make sure to update the various LICENSE and NOTICE files per Apache policy.
3. Bulk update JIRA to unassign from this release all issues that are open non-blockers. 
4. Send follow-up notification to the developer list that this was done.
5. To deploy artifacts to the Apache Maven repository create ~/.m2/settings.xml: 

<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

...