search

SwooshyCueb / strimmer

Collaborative playlisting for an internet radio station
Other
2 stars 0 forks source link

Version numbering #158

Open SwooshyCueb opened 9 years ago

SwooshyCueb commented 9 years ago

Now that the repo is public, we should probably start using version numbers and milestones

TheBlackParrot commented 9 years ago

Maybe a v[major].[revision/commits] would work well e.g. as of this comment, v0.182

SwooshyCueb commented 9 years ago

Main problem with that is that you'd have to update the version number with every commit. If we don't have some sort of file with the version number in it, this will make packaging automation difficult. If we do have the version number somewhere in the code, we will have to increment it with every commit. I know I can't trust myself to remember to do that each time.

IMO it would be better to have some sort of v[major].[minor].[micro]. We'd have milestones and goals for our major and minor releases, and micro releases would ideally be maintenance releases.

TheBlackParrot commented 9 years ago

That'll be fine then.