Create release directory and build task

[ckundo]

Per discussion with @alice, this creates a dist/ file and grunt task to build generated javascript to the directory. This way application developers can point to the stable version of the generated file on github.

Run grunt build for releases only, so we don't get overwhelmed with diffs, and be sure to git tag -f stable to bump the tag to the build rev.

[ckundo]

@alice ptal when you get a chance

[alice]

I think we should call this 'release'. 'build' to me suggests a normal build.

[alice]

Do we want any more sophisticated release options like bumping version numbers etc?

https://github.com/geddski/grunt-release looks quite promising for doing major/minor/patch numbers all automatically, and we could create a modified version of scripts/output_wrapper.txt to include the version number in the preamble. Do you feel like having a play with any of that?

[ckundo]

Sure, I'll take a look.

On Mon, Dec 2, 2013 at 6:06 PM, Alice notifications@github.com wrote:

Do we want any more sophisticated release options like bumping version
numbers etc?

https://github.com/geddski/grunt-release looks quite promising for doing
major/minor/patch numbers all automatically, and we could create a modified
version of scripts/output_wrapper.txt to include the version number in the
preamble. Do you feel like having a play with any of that?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/73#issuecomment-29667828
.

[ckundo]

@alice I'm working on a grunt-release branch. In the meantime, do you want to merge this and we can iterate on it?

[alice]

Oh yeah, sorry for not LGTMing earlier.

LGTM - I can merge, or you can.