[GH-ISSUE #68] Technical Documentation #920

New Issue

GiteaMirror · 2026-04-16T09:58:08-05:00

GiteaMirror commented

2026-04-16 09:58:08 -05:00

Originally created by @icylace on GitHub (Feb 27, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/68

With some adjustment SemVer could be useful for technical documentation such as manuals, style guides, and standards documentation. Could the intended scope of SemVer be expanded from code projects to a general versioning approach?

Originally created by @icylace on GitHub (Feb 27, 2013). Original GitHub issue: https://github.com/semver/semver/issues/68 With some adjustment SemVer could be useful for technical documentation such as manuals, style guides, and standards documentation. Could the intended scope of SemVer be expanded from code projects to a general versioning approach?

GiteaMirror closed this issue

2026-04-16 09:58:08 -05:00

GiteaMirror commented

2026-04-16 09:58:08 -05:00

@haacked commented on GitHub (Mar 13, 2013):

I think SemVer can certainly applied to these things, but I'm not sure we want to expand the scope of SemVer itself. What changes do you have in mind? Would it need to be different?

If so, perhaps we could have separate variants: SemVer for Prose for example.

@haacked commented on GitHub (Mar 13, 2013): I think SemVer can certainly applied to these things, but I'm not sure we want to expand the scope of SemVer itself. What changes do you have in mind? Would it need to be different? If so, perhaps we could have separate variants: SemVer for Prose for example.

GiteaMirror commented

2026-04-16 09:58:09 -05:00

@jeffhandley commented on GitHub (Apr 30, 2013):

I propose we close this issue until there's a concrete action item.

@jeffhandley commented on GitHub (Apr 30, 2013): I propose we close this issue until there's a concrete action item.

GiteaMirror commented

2026-04-16 09:58:09 -05:00

@Tieske commented on GitHub (Apr 30, 2013):

if I understand this correctly it doubles with #90. imo close this, continue #90.

@Tieske commented on GitHub (Apr 30, 2013): if I understand this correctly it doubles with #90. imo close this, continue #90.

GiteaMirror referenced this issue

2026-04-16 10:51:18 -05:00

[GH-ISSUE #920] Why is it called "semantic" versioning? #1443

GiteaMirror referenced this issue

2026-04-20 10:19:41 -05:00

[GH-ISSUE #920] Why is it called "semantic" versioning? #2310

GiteaMirror referenced this issue

2026-04-25 17:37:54 -05:00

[GH-ISSUE #920] Why is it called "semantic" versioning? #3292

GiteaMirror referenced this issue

2026-06-13 13:13:44 -05:00

[GH-ISSUE #920] Why is it called "semantic" versioning? #4821