Skip to content

/ express

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

Jump to bottom

Document versioning strategy #2858

Open
jasnell opened this issue Jan 18, 2016 · 3 comments
Open

Document versioning strategy #2858

jasnell opened this issue Jan 18, 2016 · 3 comments
Labels
meta

Comments

@jasnell
Copy link

@jasnell jasnell commented Jan 18, 2016

Is express using semver for versioning? It's not readily obvious. Node.js has picked up the practice of labeling issues as semver-major or semver-minor to help differentiate breaking vs additive changes. I'd recommend something similar here to help keep things organized.
@tunniclm
Copy link
Contributor

@tunniclm tunniclm commented Jan 18, 2016

It looks like semver, but I don't know for sure.

cc: @dougwilson, @ritch
@sjanuary
Copy link
Contributor

@sjanuary sjanuary commented Feb 10, 2016

Seems like it has been semver historically - see this comment and this one.
@Fishrock123 Fishrock123 added the meta label Feb 10, 2016
@dougwilson
Copy link
Member

@dougwilson dougwilson commented Feb 10, 2016

Yes, it is semver. npm forces semver semantics on any package published on it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
@dougwilson @jasnell @Fishrock123 @tunniclm @sjanuary
You can’t perform that action at this time.