You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you very much for your work on SemVerDoc! I've found it useful and I'm sure others have as well.
Recently I've worked on developing an alternative versioning scheme for documents -- following SemVerDoc's structure, but with categories that are purely qualitative (current SemVerDoc is both qualitiative and quantitative).
The new versioning scheme would be as follows:
MAJOR: Changes to the document's substance.
MINOR: Changes to the document's style but not its substance.
PATCH: Corrections of errors in spelling, grammar, or spacing.
Comparison to current SemVerDoc (as of 1.2.0):
Version
SemVerDoc
Qualitative only
MAJOR
Significant changes.
Substantive changes.
MINOR
Adding or removing information.
Stylistic changes.
PATCH
Minor changes (e.g. fixing typos).
Error corrections.
Something to consider for SemVerDoc 2.0?
The text was updated successfully, but these errors were encountered:
What is the difference between significant changes and substantive changes? Also, I add or remove information, then according to this scheme, it should always be a MAJOR increment, right? Regardless on how I feel insignificant/insubstantive it is?
Before knowing about SemVerDoc, I have been using this scheme for writing projects:
MAJOR: significant changes in root folder
MINOR: significant changes 1st-level folders
PATCH: significant changes in 2st-level folders
What is significance is up to you. For me, it may be adding or removing a file or folder. Renaming without changing the idea much may be denoted with a letter after the number (i.e. 3→3a→3b). If your root folder's structure is already stable before you apply the versioning, and you foresee that it will be stable in a far future, then you can skip the MAJOR version if you want.
This idea can be generalize to any hierarchical structure, not just limited to folder structure. For example, a hierarchical graph.
I'm not sure if this idea is useful. Any feedback is welcomed.
Thank you very much for your work on SemVerDoc! I've found it useful and I'm sure others have as well.
Recently I've worked on developing an alternative versioning scheme for documents -- following SemVerDoc's structure, but with categories that are purely qualitative (current SemVerDoc is both qualitiative and quantitative).
The new versioning scheme would be as follows:
Comparison to current SemVerDoc (as of 1.2.0):
Something to consider for SemVerDoc 2.0?
The text was updated successfully, but these errors were encountered: