github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-03-22 22:20:28 -05:00
Code Issues 118 Packages Projects Releases 4 Wiki Activity

Inconsistent language about build metadata and precedence #97

New Issue
Closed
opened 2026-02-17 11:13:25 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-02-17 11:13:25 -06:00
Owner
Copy Link

Originally created by @toddreed on GitHub (Aug 8, 2013).

Section 10 states (emphasis added):

Build metadata SHOULD be ignored when determining version precedence.

And Section 11 states:

Build metadata does not figure into precedence.

For these statements to have greater consistency, I think Section 10 should state:

Build metadata MUST be ignored when determining version precedence.

Originally created by @toddreed on GitHub (Aug 8, 2013). Section 10 states (emphasis added): > Build metadata **SHOULD** be ignored when determining version precedence. And Section 11 states: > Build metadata **does not** figure into precedence. For these statements to have greater consistency, I think Section 10 should state: > Build metadata **MUST** be ignored when determining version precedence.
GiteaMirror commented 2026-02-17 11:13:27 -06:00
Author
Owner
Copy Link

@haacked commented on GitHub (Aug 8, 2013):

Yeah, I agree. Send a PR?

@haacked commented on GitHub (Aug 8, 2013): Yeah, I agree. Send a PR?
GiteaMirror commented 2026-02-17 11:13:28 -06:00
Author
Owner
Copy Link

@pvdb commented on GitHub (Aug 21, 2013):

Does merging #151 mean this ticket can be closed?

@pvdb commented on GitHub (Aug 21, 2013): Does merging #151 mean this ticket can be closed?
GiteaMirror commented 2026-02-17 11:13:29 -06:00
Author
Owner
Copy Link

@haacked commented on GitHub (Aug 21, 2013):

Yep!

@haacked commented on GitHub (Aug 21, 2013): Yep!
GiteaMirror commented 2026-02-17 11:13:30 -06:00
Author
Owner
Copy Link

@haacked commented on GitHub (Aug 21, 2013):

@toddreed for future reference, if you add "closes #150" Where 150 is the issue number, in your commit message or in the body of the pull request, it'll close the issue automatically when the PR is merged. :)

@haacked commented on GitHub (Aug 21, 2013): @toddreed for future reference, if you add "closes #150" Where 150 is the issue number, in your commit message or in the body of the pull request, it'll close the issue automatically when the PR is merged. :)
GiteaMirror commented 2026-02-17 11:13:31 -06:00
Author
Owner
Copy Link

@toddreed commented on GitHub (Aug 21, 2013):

@Haacked Ahh—thanks for the tip.

@toddreed commented on GitHub (Aug 21, 2013): @Haacked Ahh—thanks for the tip.
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#97
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?