...
Promoting the Release
- Publish the release. Copying the layout for the previous X.Y.Z version, make a new subdirectory in SVN repository Use svn mover or copy to copy the release to 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 file
- 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.
...