[GH-ISSUE #7] Redundancy of Spec Rule 3 #2721

New Issue

GiteaMirror · 2026-04-25T16:35:20-05:00

GiteaMirror commented

2026-04-25 16:35:20 -05:00

Originally created by @efi on GitHub (Dec 22, 2011).
Original GitHub issue: https://github.com/semver/semver/issues/7

Hi.

I appreciate your efforts on giving developers a common tool for articulating code changes via version numbers. In that difficult area in the coding field fixed semantics are of real value.

Reading 1.0.0-rc.1 of your Semantic Versioning Specification I wondered, what the purpose of rule 3 is. With the exception of the given examples all specified behavior is repeated in the end of rules 8 and 9.

Could this not be condensed in any way?

Best Regards

Thomas

Originally created by @efi on GitHub (Dec 22, 2011). Original GitHub issue: https://github.com/semver/semver/issues/7 Hi. I appreciate your efforts on giving developers a common tool for articulating code changes via version numbers. In that difficult area in the coding field fixed semantics are of real value. Reading 1.0.0-rc.1 of your Semantic Versioning Specification I wondered, what the purpose of rule 3 is. With the exception of the given examples all specified behavior is repeated in the end of rules 8 and 9. Could this not be condensed in any way? Best Regards Thomas

GiteaMirror closed this issue

2026-04-25 16:35:21 -05:00

GiteaMirror commented

2026-04-25 16:35:22 -05:00

@mojombo commented on GitHub (Dec 23, 2011):

You are correct, rule 3 is redundant. I think I added those points to the 8 and 9 and then forgot to remove rule 3. Will fix.

@mojombo commented on GitHub (Dec 23, 2011): You are correct, rule 3 is redundant. I think I added those points to the 8 and 9 and then forgot to remove rule 3. Will fix.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#2721