Skip to content
Gordon Smith edited this page Dec 19, 2015 · 11 revisions

Building a release consists of the following logical steps:

  1. Ensure correct versions of third party libraries are local on the build machine.
  2. Change the version number.
  3. Build the framework.
  4. Create new "bX.Y.Z" branch.
  5. Append the build files.
  6. Tag the version.
  7. Push the branch + Tag to GitHub.

Most of these steps have been automated in gulp, as an example here are the steps used to create v1.10.0-rc2:

git fetch upstream
git checkout candidate-1.10.0
git reset --hard upstream/candidate-1.10.0
npm install
bower install
gulp bump --version 1.10.0-rc2
gulp tag-release --upstream

Note: The "bX.Y.Z" branch is needed for any project which wants to include the Framework as a submodule @ a given tag (vX.Y.Z), this is due to a limitation in git submodule, which will fail to get a tagged version if no branch contains its commit hash.