Replies: 1 comment
-
|
I don't have a preference. I'm used to just rolling with whatever is happening. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! So I'm thinking of changing the version tag scheme, currently I've bumped the major version every time I did a full rewrite (yeah, there were at least four of those) and then I basically only ever change the minor version. I never use patch.
What about bumping major every time I do feature releases, minor for fixes to those features and patch for things you won't see like doc changes or emergency bug fixes. So we start using all three parts of semver again? Treat new features and options as "major" even if they're not breaking.
That way people can pin to a major version if they like the feature set but want fixes and tiny patches to keep coming through.
My other thought is one gained from experience: Semver is imperfect enough to be fairly useless and is mostly just a convention we all keep to out of habit and we should probably just have a single incrementing number. So it'd just be v5, v6, v7 etc.
Any thoughts? For now I'll increment minor again, but I think using major for feature releases or just doing away with semver could be helpful.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions