github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-07-11 03:53:53 -05:00
Code Issues 1.0k Packages Projects Releases 4 Wiki Activity

[GH-ISSUE #347] Multipale bugs fix increment #6244

New Issue
Closed
opened 2026-06-17 04:56:19 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-17 04:56:19 -05:00
Owner
Copy Link

Originally created by @amitosdev on GitHub (Dec 19, 2016).
Original GitHub issue: https://github.com/semver/semver/issues/347

Let assume my current version is 2.0.0. We found few bugs in different modules. Those bugs are not related to each other but we are planning to fix all of them in the same version. What will be the next version number for this bug fixes? 2.0.1? 2.1.0? or even 2.0.5 (if we have for ex. 5 modules with different bugs in them)?

Originally created by @amitosdev on GitHub (Dec 19, 2016). Original GitHub issue: https://github.com/semver/semver/issues/347 Let assume my current version is 2.0.0. We found few bugs in different modules. Those bugs are not related to each other but we are planning to fix all of them in the same version. What will be the next version number for this bug fixes? 2.0.1? 2.1.0? or even 2.0.5 (if we have for ex. 5 modules with different bugs in them)?
GiteaMirror commented 2026-06-17 04:56:19 -05:00
Author
Owner
Copy Link

@scaytrase commented on GitHub (Dec 19, 2016):

The version is not a number of fixed bugs or implemented features. Version is the order (and the compatibility if speaking about semver) identifier for the release

The release numbers are incremented, so while you are not pushing a patch release for each bug the release number should be incremented once. 2.0.1 should be correct here

<!-- gh-comment-id:268074106 --> @scaytrase commented on GitHub (Dec 19, 2016): The version is not a number of fixed bugs or implemented features. Version is the order (and the compatibility if speaking about semver) identifier for the release The release numbers are incremented, so while you are not pushing a patch release for each bug the release number should be incremented once. `2.0.1` should be correct here
GiteaMirror commented 2026-06-17 04:56:20 -05:00
Author
Owner
Copy Link

@jwdonahue commented on GitHub (Nov 29, 2017):

@amitosdev unless you have additional questions, can you please close this issue?

<!-- gh-comment-id:347749449 --> @jwdonahue commented on GitHub (Nov 29, 2017): @amitosdev unless you have additional questions, can you please close this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
consensus seeking
duplicate
extend
layout
pull-request
Mirrored from GitHub Pull Request
 question
RFC
spelling/grammar
staled
update
waiting for PR
won't fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#6244
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?