...
- You MUST BE an Apache Flex committer.
- A release manager must have his public key appended to the KEYS file checked in to Git, the key published on one of the public key servers (e.g. http://pgpkeys.mit.edu), the key in their public people.apache.org home directory and their key in https://people.apache.org/keys/committer. More info can be found at http://www.apache.org/dev/release-signing.html.
- Make sure you have installed the required versions of Java, Apache Ant, Adobe AIR, Adobe Flash Player, Adobe Flash Player Debugger, Adobe Pixel Bender Toolkit and Adobe Extension Manager CS5 and you have your environment variables correctly set up for each of these. More info can be found in the README.
- Install the Rat jars, apache-rat-0.10.jar and apache-rat-tasks-0.10.jar in ${ANT_HOME}/lib or somewhere under ${user.dir}/.ant/lib. If the version of Rat that is available differs, make sure that the pattern for apache-rat in anttask.classpath is still correct. More info on Rat can be found at http://creadur.apache.org/rat/.
- You will find some handy scripts in https://svn.apache.org/repos/private/committers/tools/ and, in particular, https://svn.apache.org/repos/private/committers/tools/releases.
...
- Clone one of the last Apache Flex release JIRA issues eg https://issues.apache.org/jira/browse/FLEX-33751
or https://issues.apache.org/jira/browse/FLEX-33546 - Decide if you need an installer release at the same time as a new SDK release.
- Get people involved, email dev and user mailing lists to find out what important issues need to be fixed and if there's anything that might stop a release from happening.
...
The README page will not be visible so rename it READme.unmigrated-wiki-markup
When approved by a VOTE, the RC directory contents should be moved to the 'dist.apache.org/repos/dist/release/flex/\[flex.version\]/' repo (1).
1: http://www.apache.org/dev/release.html#upload-ci
You may also want to use the deploy_release_candidate.sh script:
...
- Publish the release. Copying the layout for the previous X.Y.Z version, make a new subdirectory in SVN repository https://dist.apache.org/repos/dist/release/flex for the release and copy over the README, RELEASE_NOTES and artifacts.
- Only remove the previous version once the mirrors have caught up (24 hours) and after the installer is updated to use the new release.
- Update JIRA. Go to the Admin section on the Flex JIRA and mark Flex X.Y.Z as released. Create the next version if that has not already been done. You may need the help of a JIRA administrator to do this.
- Update the installer configuration.
- Update Flex web site were required:
- Update and publish the doap_Flex.rdf fileunmigrated-wiki-markup
- Send separate \ [ANNOUNCEMENT\] emails using your apache.org email address, preferably signing the email with the same KEY you used to sign the release. Note: Thunderbird with Enigmail for OpenPGP seems to be the easiest to configure on the Mac. AppleMail with GPGMail is another alternative. If you are not subscribed to a list with your apache address your email the email has to be accepted by the moderator of the list before it will get posted. Make sure the email is plain text and not HTML or it may be marked as spam and rejected.
- users@flex.a.o
- dev@flex.a.o
- announce@a.o
- Update the Apache Flex home page and the Apache Flex blog with the news. Encourage people to tweet about the release.
- Update the Flex version number to be the next likely version in the code - (build.properties, many Version.as files, FlexVersion.as, MxmlConfiguration.java, VersionInfo.java). Use build/set-version.xml. See header for usage.
...
- Remove the previous version from https://dist.apache.org/repos/dist/release/flex once the mirrors have caught up (24 hours) and after the installer has been updated.
...