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?
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.
<!-- gh-comment-id:14857759 -->
@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.
if I understand this correctly it doubles with #90. imo close this, continue #90.
<!-- gh-comment-id:17257437 -->
@Tieske commented on GitHub (Apr 30, 2013):
if I understand this correctly it doubles with #90. imo close this, continue #90.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
@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.
@jeffhandley commented on GitHub (Apr 30, 2013):
I propose we close this issue until there's a concrete action item.
@Tieske commented on GitHub (Apr 30, 2013):
if I understand this correctly it doubles with #90. imo close this, continue #90.