Tags - Githubissues

dyedurham / SbManager

Installable web ui for managing Azure/Windows Service Bus

Apache License 2.0

31 stars 16 forks source link

Tags #46

Open drewfreyling opened 8 years ago

drewfreyling commented 8 years ago

I'm thinking we should probably start tagging releases. Thoughts?

lukeschafer commented 8 years ago

Only really makes sense if you plan on offering LTS or something. Every commit generates a nupkg in appveyor. I hooked my work's octopus up to my fork's appveyor build's nuget repo, so I just push new versions when something I care about has been fixed or implement (so, not that often!)

drewfreyling commented 8 years ago

@lukeschafer I'd have to disagree there.If SBManager semver'ed the releases it would allow clients to:

Not have thousands of releases because they are based on every commit
They can upgrade minor revisions with the knowledge that it is backwards compatible

This would also give SbManager the flexibility on deciding when something is ready for release.

lukeschafer commented 8 years ago

I'm all for semver. That said, semver doesn't make a whole lot of sense for websites, though I've been using:

+major: reserved for big version bumps
+minor: new features
+patch: bug fixes

What's more important than explicit tags is implementing a mechanism by which you can tie changes to builds automatically, so they correlate. This might be releases/tags, but it's not the only way, and it's not automatic. A version.md file or similar might be better