Need git-tags and release notes when we "npm publish"

[nfreear]

Hi @timcoughlan,

I think when we run npm publish, we should ideally:

1. Update a CHANGELOG.md
2. Run git tag -a X.Y.Z,

This allows us to:

1. Document new features and fixes for 3rd parties, and ourselves(!)
2. Document milestones for reporting to funders etc.;
3. Allow us to use the RawGit CDN, as backup for Unpkg ~~ https://rawgit.com/

I have an initial CHANGELOG.md to commit ...

Nick

---

Added: Google spreadsheet documenting proposed tags.

[nfreear]

Google spreadsheet documenting proposed tags.

[nfreear]

Hi,

We may want to use Travis-CI to do the npm publish step ...:

• GitHub: mdn/browser-compat-data .travis.yml ~ deploy: ..
• Travis-CI docs: deployment / npm
• E.g. travis-ci: mdn/browser-compat-data ~ job with deploy @v0.0.55

N.