-
Notifications
You must be signed in to change notification settings - Fork 63
Building a Release
Gordon Smith edited this page Apr 23, 2016
·
11 revisions
Building a release consists of the following logical steps:
- Ensure correct versions of third party libraries are local on the build machine.
- Change the version number.
- Build the framework.
- Create new "bX.Y.Z" branch.
- Append the build files.
- Tag the version.
- 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 && npm update && bower install && bower update
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.