Skip to content
This repository has been archived by the owner on Sep 11, 2020. It is now read-only.

Versioning #37

Open
chrissnyder opened this issue May 15, 2014 · 1 comment
Open

Versioning #37

chrissnyder opened this issue May 15, 2014 · 1 comment

Comments

@chrissnyder
Copy link
Contributor

Any group opinions on the versioning scheme?

Normally I think typical semantic versioning works fine, but last week I made a couple of commits, versioning each one as a separate release. Does this make sense? Or should I smash numerous backward compatible changes/fix into a single release?

@brian-c
Copy link
Contributor

brian-c commented May 15, 2014

Each commit doesn't need a separate tag. Commits have IDs. If you really want to refer to a specific commit, use that.

I think it's a waste of time to tag Git commits. The package.json version is the one that matters.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants