Add Tooling to Release Process

[MattSurabian]

Could have grunt tasks that make a versioning workflow interactive or flagable. This would help users who are new to git with their build process.

[MattSurabian]

Maybe the build task takes some flags that will bump the version and cut a tag?

[tkellen]

npm version [patch,minor,major]?
On Apr 11, 2016 8:11 PM, "Matthew Surabian" notifications@github.com
wrote:

Maybe the build task takes some flags that will bump the version and cut a
tag?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#3 (comment)

[MattSurabian]

Yep that's what I'd suggest we use but automating that as part of a production build would make it really easy for folks not used to doing strict versioning

[mzgoddard]

Automation would be a good step but it can't get rid of teaching people strict versioning. The automation needs some meta data to know how to version a change and developers need to author that meta data.

[labond]

Look at this again after writing git post

[kadamwhite]

This is specifically about cutting releases (preparing code for release), not deploying releases (publishing code). grunt version might look through all your commits in your code up until the last version tag, and flag based on "minor" or "major" (or some other standard) to determine how to increment version numbers. May build upon work @mzgoddard has done in boxart/boxart#6