I’ve always been terrible at versioning software. Terrible. So terrible, in fact, that I’ve never done it. Renaissance is no exception. People have always exhorted me to do it, and, well, I guess I’m caving in…
If you’ve read more than a handful of the posts on this blog, by now you’ll be aware of my mass and chronic ignorance when it comes to coding and software development conventions. Versioning is no exception to this rule. I strongly suspect that my repository can handle it for me, but I lack the inclination to find out. And besides, I’m contrary, so I’ve come up with my own system.
For new features and feature upgrades we have,
- tiny: 0.05 points
- very minor: 0.5 points
- minor: 1 point
- normal: 2 points
- major: 3 points
- very major: 5 points
- massive: 15 points
Whenever we hit 30 points, we can score a revision after the dot. We’ve got the same system for bug fixes, with the bug feature count coming after the second dot. I also reserve the right to declare a new version whenever I feel like it.
So, I’ve declared the current version of Renaissance version 0.1.0a (the ‘a’ being for alpha) and have commenced the counting. I think the low version number’s kind of funny, as Renaissance has been in development for something like five years. Oh well.
Anyway, what do you think? I’m pretty sure the gods of coding conventions are frowning on me right now… 
No related posts.
{ 2 comments… read them below or add one }
Gleb 02.25.09 at 4:17 am
“Version numbers of [Donald Knuth's] TeX software approach the transcendental number π, in that versions increment in the style 3, 3.1, 3.14. 3.141, and so on. Version numbers of Metafont approach the important number e similarly.”
http://en.wikipedia.org/wiki/Donald_Knuth
Candid 04.11.11 at 6:18 pm
Ppl like you get all the brains. I just get to say thanks for he anrwse.