Page History

...

• Make a clean checkout of the UserALE.js repository (ensuring that there are no local modifications): 

  Code Block
  $ git clone https://git-wip-usgitbox.apache.org/repos/asf/incubator-flagon-useralejs.git $ git pull --rebase # assumes that the Apache canonical repository is the default upstream for your master - amend if necessary $ git checkout -b $VERSION_NAME

  
  

• Make sure all unit and integration tests are passing. 
  • All tests must pass... if they do not then they need to be fixed before further progress can be made. Each flagon subproject you are attempting to release should contain a README with details on how to run the tests. If it does not, submit a pull request before progressing.
• Update the CHANGELOG.md to reflect the current release, this may also be required for other essential files such as NOTICE, README etc. Ensure all of these files are accurate and up-to-date. It is also advised to include the JIRA release report in CHANGES.md. This makes it very easy for people to see the relevant changes for this release bundle.
• Now change the version numbers in this branch in package.json.

• If you have never made a flagon UserALE.js release, you are required to append your gpg key to the flagon KEYS file. This will then be used to sign all release artifacts. Much more about this can be found here http://apache.org/dev/release-signing.html

  Note
  This is an extremely important part of the release procedure. It is essential to get it right and that all subsequent release managers' KEYS are associated with this file.

  
  

• If any changes based on the above have been made, then commit them to the VERSION branch.

Update

...

master to reflect future version

The master branch will now need updating to refer to the next planned version. (This step is not required if making a “milestone” release or similar.) The release notes should be cleared out and the version history augmented with the new version. Also ensure that package.json and the example index.html reflect the new version.

$ git add . && git commit -m "Change version to $NEW_MASTER_VERSION"

Switch back to the master current  release branch

Move back to the release version.

...

$ git push userale-js $VERSION_NAME && git push apache-git rel/apache-flagon-userale-js-${VERSION_NAME}-rc${RC_NUMBER}

$ mkdir apache-flagon-useralejs-incubating-${VERSION_NAME}-rc${RC_NUMBER}

$ svn add apache-flagon-useralejs-incubating-${VERSION_NAME}-rc${RC_NUMBER}
$ svn commit --username $SVN_USERNAME --no-auth-cache --message "Add apache-flagon-useralejs-incubating-${VERSION_NAME}-rc${RC_NUMBER} to dist/dev/flagon"

...

• In the JIRA Administration Interface, go to
  • Versions
  • for the release tag you've just released, add a release date and then release it
• Update the DOAP to reflect the release