How to release a new version

1. Update GitHub issue tracker for release.

   • Create a milestone in GitHub for the next version.
   • Bump any open tickets to the next version.
   • Mark the current release milestone as closed.

2. Ensure that you are in the master branch.

3. Run grunt bump or grunt bump:minor.

   • Updates the package.json and bower.json using semver.

4. Run grunt release.

   • This will build the dist folder and update version numbers within markdown files. Visually check that dist file banners have the new version and commit.

5. Commit.

   • Use release x.x.x as commit message.

6. Upload contents of dist folder to Fuel CDN server via FTP.

7. Push to origin:master.

8. Checkout current major.x branch (example: 3.x) and merge master branch into it, then push changes to origin.

9. Create tag locally. git tag -a x.x.x -m 'vx.x.x'. Publish tag to Github: git push origin x.x.x. The tag commit should exist in the major.x branch.

10. Write release notes (see below).

11. Update Marketing Cloud Theme documentation found in Fuel UX's gh-pages branch.

12. Fix GitHub issue tracker to know about the release

    • Create a milestone in GitHub for the NEXT version.
    • Move any open tickets for released version to the next version.
    • Mark the milestone as closed.

13. Announce

• Tweet via @ETfuel account

##Release Notes Write Github release notes for the tag, using this template:

• Pull Requests within milestone
  • https://github.com/exacttarget/fuelux-mctheme/issues?q=milestone:x.x.x+is:pr

(and anything important about this release)

New Features and improvements

(#ticketnumber and a human-readable description of the pull request, usually the pull request title. If the ticket title doesn't make sense, either edit the ticket directly, or provide an alternative title here. Be sure to include the name of the controls modified at the end in brackets.)

#700 - deselected and selected events added [tree] 

Bug Fixes

Upgrade Notes

(anything special that needs to be called out)