fix bug - new feature same time #331

New Issue

GiteaMirror · 2026-02-17T11:51:53-06:00

GiteaMirror commented

2026-02-17 11:51:53 -06:00

Originally created by @elmer120 on GitHub (Aug 8, 2018).

Hi to all!

I have a question.
In the previous state of 1.0.0, if for example the software is at 0.1.1-alpha.
If I do this I'll correct a bug but at the same time add a new feature.

Is it correct to go from 0.1.1-alpha to 0.2.0-alpha?

thanks

Originally created by @elmer120 on GitHub (Aug 8, 2018). Hi to all! I have a question. In the previous state of 1.0.0, if for example the software is at 0.1.1-alpha. If I do this I'll correct a bug but at the same time add a new feature. Is it correct to go from 0.1.1-alpha to 0.2.0-alpha? thanks

GiteaMirror closed this issue

2026-02-17 11:51:53 -06:00

GiteaMirror commented

2026-02-17 11:51:54 -06:00

@grv87 commented on GitHub (Aug 12, 2018):

@elmer120, in before-1.0.0 state I personally follow all the rules as in post-1.0.0 except Rule 8 about breaking changes.
If you fix a bug and add a feature then Rule 7 replaces Rule 6, and you should increase minor and reset patch to 0.
So, you are correct. You should go with 0.2.0.
About alpha pre-release label: if you follow current version of SemVer strictly, then it is not required. All versions before 1.0.0 are pre-releases, no need to signify that.
But if you think that magic zero rule could be mistake then alpha pre-release label is required.

@grv87 commented on GitHub (Aug 12, 2018): @elmer120, in before-1.0.0 state I personally follow all the rules as in post-1.0.0 except Rule 8 about breaking changes. If you fix a bug and add a feature then Rule 7 replaces Rule 6, and you should increase minor and reset patch to 0. So, you are correct. You should go with `0.2.0`. About `alpha` pre-release label: if you follow current version of SemVer strictly, then it is not required. All versions before `1.0.0` are pre-releases, no need to signify that. But if you think that [`magic zero` rule could be mistake](https://github.com/semver/semver/issues/221) then `alpha` pre-release label is required.

GiteaMirror commented

2026-02-17 11:51:55 -06:00

@jwdonahue commented on GitHub (Aug 18, 2018):

@elmer120, yes. Even if you added fifty new features and fixed a thousand bugs, you're only required to bump the minor field by one in this case. Unless you have any further questions, please close this thread at your earliest possible convenience.

In the future, you may find that StackOverflow already has answers to many questions similar to yours. Just search on the [semver] tag. If you don't find the answer, ask your question there (include the Semantic Versioning tag) and somebody will likely respond within hours, rather than days.

@jwdonahue commented on GitHub (Aug 18, 2018): @elmer120, yes. Even if you added fifty new features and fixed a thousand bugs, you're only required to bump the minor field by one in this case. Unless you have any further questions, please close this thread at your earliest possible convenience. In the future, you may find that StackOverflow already has answers to many questions similar to yours. Just search on the [semver] tag. If you don't find the answer, ask your question there (include the Semantic Versioning tag) and somebody will likely respond within hours, rather than days.

GiteaMirror commented

2026-02-17 11:51:56 -06:00

@jwdonahue commented on GitHub (Aug 23, 2018):

@elmer120, unless you intend to issue a pull request or have further questions, please close this issue at your earliest possible convenience.

Thank you.

@jwdonahue commented on GitHub (Aug 23, 2018): @elmer120, unless you intend to issue a pull request or have further questions, please close this issue at your earliest possible convenience. Thank you.

GiteaMirror commented

2026-02-17 11:51:57 -06:00

@jwdonahue commented on GitHub (Aug 25, 2018):

@elmer120, is there anything else you need help with?

@jwdonahue commented on GitHub (Aug 25, 2018): @elmer120, is there anything else you need help with?

GiteaMirror referenced this issue

2026-02-17 11:53:17 -06:00

Resolve the "what's being versioned" ambiguities in the spec. #342

Sign in to join this conversation.