Documented release process

twolfson / google-music.js

Browser-side JS library for controlling Google Music

The Unlicense

47 stars 6 forks source link

Documented release process #25

Closed twolfson closed 8 years ago

twolfson commented 8 years ago

For releases, I have been using foundry to manage the multiple steps. It's super helpful when we need to re-publish when there was a mistake (e.g. typo in README).

foundry release 1.0.0
foundry release 1.0.1

In this PR:

Added documentation for foundry
Added npm run build to foundry release steps (to guarantee most recent dist directory)

/cc @gmusic-utils/gmusic-js

chrismou commented 8 years ago

Weird - I didn't get a notification about this

I'll check it out shortly. Just en route home

twolfson commented 8 years ago

Bump on this PR =/

jacobwgillespie commented 8 years ago

LGTM :+1:

twolfson commented 8 years ago

Going to wait until the end of the weekend for @chrismou to chime in. Otherwise, going to land it

chrismou commented 8 years ago

All looks good to me :shipit:

twolfson commented 8 years ago

This has been merged/released in 4.0.2 :tada:

chrismou commented 8 years ago

@twolfson Out of interest, do you tend to go for a release per bug/feature/etc? Or would there be some cases where you'd store them up and release a bunch at once?

twolfson commented 8 years ago

I usually do releases per bug/feature/PR. The rare case where I group PRs for a single release is for multiple breaking changes (e.g. changing many function signatures) but I prefer to avoid that.