Versions Compared

Old Version 80

changes.mady.by.user Erik de Bruin

Saved on

compared with

New Version Current

changes.mady.by.user Alex Harui

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Prerequisites

  • You 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

Prerequisites

Pre

...

-release

  • Clone one of the last Apache Flex release JIRA issues eg https://issues.apache.org/jira/browse/FLEX-

    34560

    34661 (4.

    14

    15.0)

  • 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.

Preparing Sources

  • Follow this guide to prepare and engage the community. 

 

The rest of this document describes the actions the RM must take to prepare the SDK for the various release steps:

Preparing Sources

  • Ensure the LICENSE 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 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 pushcheckout -u b releaseX.Y.Z
git push -u origin develop:releaseX.Y.Z
Z 

    Another RM originally suggested using the below command instead, but that caused the develop branch to track the release branch and made merging more confusing laterCreate a new directory, change to it and check out the develop 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 httpsclone https://git-wip-us.apache.org/repos/asf/flex-sdk.git .

  • Checkout the new release branch with:

    Code Block
    git checkout releaseX.Y.Z

     

    Most of the rest of these steps have been placed in an Ant script so you can run one script and not have to keep referring back to these steps and worry about typing the commands correctly.  See Release Manager and Release Voter Ant Scripts for details on the scripts

     

  • Tag the release

    Code Block
    git tag -

    Tag the release

    Code Block
    git tag -a apache-flex-sdk-X.Y.ZRC1ZRCx -m 'Apache Flex X.Y.Z RC1RCx'
git push --tags

You may also want to use the make_release_branch.sh script:

Code Block
make_release_branch.sh X.Y.Z

Building the Release

  • Build the source and binary packages.

    Code Block
    cd build
./build_release.sh

    The packages can be found in the out subdirectory.

...

  • Check the RAT log in rat.log to make sure no binaries or unlicensed files where inadvertently introduced into the source kit.
  • Other ant targets you may want to become familiar with are source-release, source-package, binary-release, binary-package and rat-check. These are useful if you modify the files in the kit and you want to short circuit some of the build process to test your changes.

Verifying the Kits

  • Verify the asc and md5 signatures for both kits then unzip both the source and binary kits.
    You may also want to use the check_sigs.sh script:

    Code Block
    check_sigs.sh X.Y.Z RC
  • Verify that the name, version and build number are correct in flex-sdk-description.xml.

  • Verify that the source files in the zip kit have Windows line endings and the source files in the OSX kit has Unix line endings.

    Code Block
    cd apache-flex-sdk-X.Y.Z-src
ant main checkintests

  • Verify that the components in the binary kit can be built.

    Code Block
    cd apache-flex-sdk-X.Y.Z-bin/frameworks
ant
  • Double-check the spelling and grammar in README, LICENSE and RELEASE_NOTES files.
  • Verify that the SDK can be used with Adobe Flash Builder version 4.6 and 4.7. See ide/flashbuilder/README_integration_with_Adobe_FlashBuilder.txt for the list of checks that Adobe Flash Builder performs on the Apache SDK to ensure compatibility of the SDK with Flash Builder. You can use ide/flashbuilder/makeApacheFlexForFlashBuilder.sh in either the binary kit or the source kit build with "ant main frameworks-rsls".

Testing the Release

The entire mustella test suite should be run.

Signing the Release

The build script will prompt for the password to your KEY and sign the release.

...

Code Block
cd build
cp ./sign_and_hash.sh ../out
cd ../out
./sign_and_hash.sh

Staging the Release

The release manager should stage the release candidate (RC) by placing it in the sdk directory of the 'dist.apache.org/repos/dist/dev/flex/' SVN repo (1).

...

Code Block
deploy_release_candidate.sh X.Y.Z RC

...

The Vote

Start the vote on the flex-dev mailing list

...

; encourage each contributor to take the following steps before voting:

  1. download the source code package.
  2. verify the the signature on the package
  3. compile the source

...

  1. code
  2. test the resulting executables on their own platform.
  3. Optional: download the binary package, build the framework, and ensure the binary distribution passes basic tests.

Wait for the Results

Votes on whether a package is ready to be released follow a format similar to majority approval - except that the decision is officially determined solely by whether at least three more +1 votes than -1 votes were registered. Releases may not be vetoed. Generally the community will table the vote to release if anyone identifies serious problems, but in most cases the ultimate decision, once three or more positive votes than negative votes have been garnered, lies with the release manager. The specifics of the process may vary from project to project, but the 'minimum of three +1 votes' rule is universal.

The list of binding voters is available at http://flex.apache.org/team.htmlThe RM may call the result of the vote no sooner than 72 hrs. after it was started. Since a release vote is 'Majority Approval', a release is approved if it gets at least 3 binding +1 votes and more binding +1 than -1 votes. Binding votes are cast by PMC members. For a complete list of PMC members, see http://people.apache.org/committers-by-project.html#flex-pmc.

If the vote is successful, post the result to the flex-dev list including dev@ list (include the number of binding and non-binding votes.
If the vote is successful, then promote ); promote and distribute the release. See Promoting the Release.

If the vote is unsuccessful, fix the issues and restart the process. See Canceling the Release.

Canceling the Release

If the vote fails, or you decide to redo the release:

...

  • 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
tag_release.sh X.Y.Z

Merging back

...

into develop and master

If the release produces Maven artifacts, it is best to merge to master first, then update Maven versions, then merge to To merge the released code back into the develop branch.

  • Check out the develop branch

    Code Block
    git checkout developmaster
git pull

  • Test merging the release branch into the develop master branch

    Code Block
    git merge --no-commit ---no-commitno-ff releaseX.Y.Z

  • If no issues merge the release branch into the master branch

    Code Block
    git merge --no-ff releaseX.Y.Z

  • If no issues merge the release branch into the develop branch

    Code Block
    git merge --no-ff releaseX.Y.Z

  • Check merged changes back into the remote master branch

    Code Block
    git push

  • Change the maven version and delete the backup files

    Code Block
    mvn versions:set -DnewVersion=X.Y.(Z+1)-SNAPSHOT
find . -name *.versionsBackup -delete

  • Commit it

    Code Block
    git add .
git commit -m "update maven versions to next version" 

    Check merged changes back into the remote develop branch

    Code Block
    git push

To merge the released code back into the master branch, repeat the above steps using 'master' instead of 'develop', repeat the above steps using 'develop' instead of 'master'.  Also update the build.properties that have the latest version number in most of our repos, and update version numbers the sdk-installer-config-4.0.xml file that the Installer uses for the nightly builds.

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.

Clean up old version

Reference: