Table of Contents
Prerequisites
- You must have to be an Apache Flex committer., as the Release Manager (RM) needs to have write access to both the Git and SVN repos.
- An RM 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 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-34560 34661 (4.1415.0)
Decide if you need an installer release at the same time as a new SDK release.
- Follow this guide to prepare and engage the community.
...
- Ensure the LICENSE and NOTICE files are current. Check that the years in the copyright statement in the NOTICE file are correct.
- Update the README. Make sure the list of dependencies and their licenses is still accurate. Update the version number.
- Update RELEASE_NOTES. Include list of bugs that were fixed in this release.
- If it hasn't been done already, make sure the version information has been updated in build.properties, modules/compiler/src/java/flex2/tools/VersionInfo.java, modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.java, and frameworks/projects/framework/src/mx/core/FlexVersion.as. The script build/set-version.xml will do most of this for you and remind you to edit MxmlConfiguration.java and FlexVersion.as by hand. Usage (from SDK root): "ant -f ./build/set-version.xml -Dmajor=4 -Dminor=15". Updating build.properties will update the name of the packages to apache-flex-sdk-${release.version}-src and -bin. As part of the release build, the frameworks/**/Version.as files will be updated with the release version and build number.
- It is highly recommended that you do a release build and Mustella run in the develop branch and any fix any known build process issues before branching for the release.
...
- Ensure your local 'develop' branch is up-to-date
Make sure that the path that the source is checked out to does not contain spaces. Create a new remote 'release' branch
Code Block git push -u origin develop:releaseX.Y.Z
Create a new directory, change to it and check out the develop branch.
Code Block git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git .
Checkout the new release branch with:
Code Block git checkout releaseX.Y.Z
Tag the release
Code Block git tag -a apache-flex-sdk-X.Y.ZRC1ZRC0 -m 'Apache Flex X.Y.Z RC1RC0' git push --tags
You may also want to use the make_release_branch.sh script:
...