Prepare for next release development #243
Conversation
| @@ -1,7 +1,7 @@ | |||
| { | |||
| "name": "library-webservices-status", | |||
| "private": true, | |||
| "version": "1.5.2-rc2", | |||
| "version": "1.5.3", | |||
There was a problem hiding this comment.
I don't know if we have a policy/practice on this.
Do we want to have next releases be something more like 1.5.3-SNAPSHOT?
Then when a release is cut (or a release candidate) then that -SNAPSHOT is changed or removed.
There was a problem hiding this comment.
https://docs.npmjs.com/about-semantic-versioning
https://semver.org/
I think we want to at least follow the semantic versioning referenced by npmjs docs. The SNAPSHOT semantics I find more commonly used with Maven artifacts.
As we are not producing any published libraries with our AngularJs apps, I am not sure we should even bother with rc or beta as they are not published for use as a dependency. I'd rather simplify for apps to just increment to the next anticipated version without rc, beta, or snapshot.
No description provided.