Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SemVer badge/shield. #104

Closed
jmalloc opened this issue Jun 6, 2013 · 9 comments
Closed

SemVer badge/shield. #104

jmalloc opened this issue Jun 6, 2013 · 9 comments

Comments

@jmalloc
Copy link

jmalloc commented Jun 6, 2013

Just a quick thought I had - I think it would be beneficial to have a small, official "SemVer" icon/badge/shield to display on websites, README files, etc, that indicates a project uses semantic versioning. It's often hard to tell from tag names alone, and this would remove any doubt.

@Tieske
Copy link
Contributor

Tieske commented Jun 6, 2013

I would prefer an optional tag eg.a trailing sv (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer. This would make it a lot easier to transition from a proprietary versioning schedule to a standard semver based schedule.

For human communications though I like the idea of a batch.

@BitDrifter
Copy link

+1 for both Ideas.

@jmalloc
Copy link
Author

jmalloc commented Jun 24, 2013

A friend of mine linked me the image below, which is a modified example from the "shields as a service" issue on olivierlacan/shields. I like the idea of it stylistically matching badges used by other projects (Travis CI, etc), at the very least in terms of dimensions.


original url: http://calm-shore-6115.herokuapp.com/?label=semver&value=2.0.0-RC1&color=green

@chadwhitacre
Copy link

I would prefer an optional tag eg.a trailing sv (space sv) which would allow existing systems to automatically determine whether a version could be parsed as SemVer.

@Tieske There are multiple versions of SemVer though. How would you communicate that?

@Tieske
Copy link
Contributor

Tieske commented Aug 11, 2013

using the sv postfix, it could simply be appended; 1.2.3 sv2.0.0 package version 1.2.3 based on SemVer 2.0.0.

@chadwhitacre
Copy link

@Tieske Noted on badges/shields#36.

@AaronLasseigne
Copy link

👍 A badge would be great.

@rlidwka
Copy link

rlidwka commented Dec 15, 2013

Will 1.2.3+sv be good enough for this?

Strong "-1" for badges, all of them, because most of them are essentially a web bugs tracking users activity on the internet.

@haacked
Copy link
Contributor

haacked commented Jul 1, 2014

I'm not sold on the idea, but if we're going to discuss a badge, it seems a PR is a good place. Closing due to #126

@haacked haacked closed this as completed Jul 1, 2014
qub1750ul pushed a commit to qub1750ul/versioning that referenced this issue Jul 10, 2021
Corrects issue semver#93, Title of 2.0.0-rc.2 is incoherent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants