Repository navigation
document versioning philosophy #174
Description
I believe we are following semver so we should mention that somewhere and link to http://semver.org/
{{ message }}
I believe we are following semver so we should mention that somewhere and link to http://semver.org/
Activity
ryanseys commentedon Sep 4, 2014
Are we going to provide versioned docs? At least for major & minor releases (not patch releases)
silvolu commentedon Sep 4, 2014
That's the plan. Today I should have time to work on the build script.
stephenplusplus commentedon Sep 21, 2014
We now have versioned docs 👍
I don't think it's necessary to make any specific mention of semver. It's implied since we're a node module and registered on npm. If that's not the popular opinion, feel free to re-open. Just trying to clean up the backlog :)
chore: nyc ignore build/test by default (#174)
docs: update contributing path in README (#174)
build: update protos (#174)
chore: nyc ignore build/test by default (#174)
docs: update links in contrib guide (#174)
Release v0.5.0 (#174)
37 remaining items
fix(sessionPool): fix race condition (#174)
fix: get eslint passing (#174)
update to .nycrc with --all enabled (#174)
test: modernize mocha config (#174)
test: modernize mocha config (#174)
chore(deps): lock file maintenance (#174)
chore(nodejs): use cloud-rad publication process (#1112) (#174)
build: update linkinator config (#174)
build: update linkinator config (#174)
Update gcs-resumable-upload (googleapis#174)
Issue#137 name vs id fix for instance.js (#174)
Issue#137 name vs id fix for instance.js (#174)
chore(deps): lock file maintenance (#174)
Issue#137 name vs id fix for instance.js (#174)
Issue#137 name vs id fix for instance.js (googleapis#174)