Modify preamble to clearly identify SemVer as being based on existing practices #32

New Issue

GiteaMirror · 2026-02-17T11:04:01-06:00

GiteaMirror commented

2026-02-17 11:04:01 -06:00

Originally created by @TheRealEdwardCullen on GitHub (Jul 27, 2012).

As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work...

Should be something like:

As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules based on pre-existing widespread common practices in use in both closed and open-source software - I am merely formalising them in a rigourous way.

For this system to work...

Reasoning: Make it clear up-front that you didn't "just make this up".

Originally created by @TheRealEdwardCullen on GitHub (Jul 27, 2012). > As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work... Should be something like: > As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. These rules based on pre-existing widespread common practices in use in both closed and open-source software - I am merely formalising them in a rigourous way. > > For this system to work... Reasoning: Make it clear up-front that you didn't "just make this up".

GiteaMirror closed this issue

2026-02-17 11:04:01 -06:00

GiteaMirror commented

2026-02-17 11:04:02 -06:00

@icylace commented on GitHub (Feb 22, 2013):

Maybe it also needs to be clear that SemVer is not limited by what common practice is if in the future common practice differs from what the SemVer spec is.

For example, what if one day marketing version numbering becomes more prevalent than technical version numbering?

@icylace commented on GitHub (Feb 22, 2013): Maybe it also needs to be clear that SemVer is not limited by what common practice is if in the future common practice differs from what the SemVer spec is. For example, what if one day marketing version numbering becomes more prevalent than technical version numbering?

GiteaMirror commented

2026-02-17 11:04:03 -06:00

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

Could you submit this as a PR? It's easier to manage that way. Thanks!

@haacked commented on GitHub (Mar 13, 2013): Could you submit this as a PR? It's easier to manage that way. Thanks!

GiteaMirror referenced this issue

2026-04-16 09:54:23 -05:00

[GH-ISSUE #32] Needs example RegExp #890

GiteaMirror referenced this issue

2026-04-20 09:19:26 -05:00

[GH-ISSUE #32] Needs example RegExp #1757

GiteaMirror referenced this issue