How to release a new version

1. Create issue for change logs titled change log for x.x.x assigned to version

2. Start writing release notes (see below).

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

4. git checkout master && git pull upstream master

5. git checkout 1.x && git pull upstream:1.x

6. git merge master

7. grunt release or grunt release --minor

   • Updates the package.json and bower.json using semver. 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.

8. git add dist && git add *.md && git add *.json && git commit -m 'release x.x.x'

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

10. git tag -a x.x.x -m 'vx.x.x' && git push upstream x.x.x

    • The tagged commit should be in the release branch only. Create and publish tag.

11. git checkout master && git merge 1.x && git push upstream master

• should be a clean fast-forward

1. Finish release notes (see below).

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

3. Announce

• Tweet via @FuelUX 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)