...
- 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. Updating build.properties will update the name of the packages to apache-flex-sdk-${release.version}-incubating-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.
...
Creating a Release Branch
- 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.ZRC1 -m 'Apache Flex X.Y.Z RC1' git push --tags
Building the Release
- Build the source and binary packages.
The packages can be found in the out subdirectory.Code Block cd build ./build_release.sh
...
- Remove the release candidate from the staging area.
- Make required changes
- Tag the new release candidate
Code Block git tag -a apache-flex-sdk-X.Y.ZRCx -m 'Apache Flex X.Y.Z RCx' git push --tags - Continue with creating a new release. See Building the Release.
Tagging the Repository
Tag the release in git, the tag name and commit message with the relevant release information. You must ensure the source in the package matches the tag.
| Code Block |
|---|
git tag -a apache-flex-sdk-X.Y.Z -m 'Apache Flex X.Y.Z' git push --tags |
Merging back into develop and trunk
...
To merge the released code back into the master branch, repeat the above steps using 'master' instead of 'develop'.
Tagging the Repository
Tag the release in git, the tag name and commit message with the relevant release information. You must ensure the source in the package matches the tag. Make sure you're on the 'master' branch when applying the tag.
...
Promoting the Release
- 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:
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.
...