-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 3.0.0 #47
Comments
We should follow semver IMHO. If there're breaking changes, yes. Otherwise quantity of changes shouldn't be a criteria. |
the general rule of them is if you push a new feature or capability but don't break the existing api, you can update the minor version. If you're not adding anything new, not breaking the api, update the patch number. |
At the very least we're going to require alexa-app >= 2.4.0, so maybe a major bump is warranted here. I'm also tempted to release it as 2.5.0, just because that will match alexa-app 2.5.0, but maybe that's unnecessary. Appreciate everybody's thoughts. Only waiting on #64 to be merged and we can cut a release here. |
I got some docs in #69, otherwise I feel this is ready to go right on the tail of an alexa-app release (will need to change package.json minimum version for alexa-app). |
Released as 3.0.0. |
Considering how many changes we've all contributed to this library, wouldn't it make sense to bump the version to 2.4.0 from 2.3.1, instead of 2.3.2?
The text was updated successfully, but these errors were encountered: