[GH-ISSUE #288] semver.org 2.0.0 last FAQ uses 'semver' while master branch 2.0.0 uses 'SemVer' #5325

New Issue

GiteaMirror · 2026-06-15T11:37:57-05:00

GiteaMirror commented

2026-06-15 11:37:57 -05:00

Originally created by @hyiltiz on GitHub (Nov 30, 2015).
Original GitHub issue: https://github.com/semver/semver/issues/288

I think the master branch version should be labeled as 2.0.1 or something else; since no software should be different while having the same versions. Also, it should be great to directly host through github, or make a mirror sync for the web server with master branch here.

Originally created by @hyiltiz on GitHub (Nov 30, 2015). Original GitHub issue: https://github.com/semver/semver/issues/288 I think the master branch version should be labeled as 2.0.1 or something else; since no software should be different while having the same versions. Also, it should be great to directly host through github, or make a mirror sync for the web server with master branch here.

GiteaMirror added the duplicate label 2026-06-15 11:37:57 -05:00

GiteaMirror closed this issue

2026-06-15 11:37:58 -05:00

GiteaMirror commented

2026-06-15 11:38:00 -05:00

@jwdonahue commented on GitHub (Jan 21, 2020):

I think the master branch version should be labeled as 2.0.1 or something else;

Yes. We should probably be somewhere in the 2.yy.zzz range by now.

Have you tried forking semver/semver.org? That's the repo that produces the https://semver.org/.

@jwdonahue commented on GitHub (Jan 21, 2020): > I think the master branch version should be labeled as 2.0.1 or something else; Yes. We should probably be somewhere in the 2.yy.zzz range by now. Have you tried forking [semver/semver.org](https://github.com/semver/semver.org)? That's the repo that produces the [https://semver.org/](https://semver.org/).

GiteaMirror commented

2026-06-15 11:38:01 -05:00

@jwdonahue commented on GitHub (Jan 21, 2020):

@hyiltiz, this a very old issue. Do you intend to issue a PR to fix it? If not, and if you don't have any further questions, please close this thread at your earliest possible convenience.

Thank you.

@jwdonahue commented on GitHub (Jan 21, 2020): @hyiltiz, this a very old issue. Do you intend to issue a PR to fix it? If not, and if you don't have any further questions, please close this thread at your earliest possible convenience. Thank you.

GiteaMirror commented

2026-06-15 11:38:02 -05:00

@hyiltiz commented on GitHub (Jan 22, 2020):

I'd love to submit a PR but not sure which abbr. is preferred among semver SemVer Semver for Semantic Versioning. They all appear in the document in various places.

@hyiltiz commented on GitHub (Jan 22, 2020): I'd love to submit a PR but not sure which abbr. is preferred among `semver` `SemVer` `Semver` for `Semantic Versioning`. They all appear in the document in various places.

GiteaMirror commented

2026-06-15 11:38:03 -05:00

@alexandrtovmach commented on GitHub (Jun 10, 2020):

@hyiltiz Thanks for report, I'll take a look soon
Closed as duplicate of #407

@alexandrtovmach commented on GitHub (Jun 10, 2020): @hyiltiz Thanks for report, I'll take a look soon Closed as duplicate of #407

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#5325