What, if any, are the conventions for numbering the versions of themes, modules, builds, etc.?
Author's choice. But basically it is MajorVersion.MinorVersion, beyond that yer on your own.
I try to take in to consideration how "finished" it feels, and if I plan on updates.
Yeah, what xcal said. If the first release of a theme is pretty much the way I want it I usually call it 1.0. Minor subsequent fixes can be released as 1.01 and so on. If, on the other hand, the theme is a messy test release (features missing or broken etc.) I'll call it 0.1. That gives you more room for improvements before the theme goes final.
Yeah that makes sense xcal/West, that is generally how everyone else does it too (come to expect a 0.1 will be unfinished)
I switched to using major.minor.bugfix for modules because it's hard to limit yourself to 10 bugs.
yeah, a minor release would contain many bugfixes,
Why is the core versioning so munted then? (o.24.7, no major releases, 24 minors, and 7 bugfixes?)
Open-source projects are often versioned more to keep track of changes than to show that they are release-ready. Many a stable and reliable app is still in the 0.1 range.
Well, if thats the case, I think there is something wrong with the versioning of many stable apps ;)
Why not just call it 1.0 ? IMHO its an indicator of work history and everything that goes with it (a 1.0 app should be more stable/reliable than a 0.4 app, IMO)
And LS has been stable for ages...
...the objective was never to sell anyone on it. So, if it isn't totally rewritten, why make a major version change?
I know that the discussion took place when we dropped the b from the versioning that LS should never hit a 1.0 release. LS was to remain in a never ending beta lifecycle.
weird...
DeV: Is the point of doing that to detract n00bs and attract geeks?
if so, it doesnt seem to be working... (or is it just ls.net =P )
nah...had to do with not setting the expectation that it would ever be finished.
I thought the whole point of open-source was that there was no such thing as a finished product.
What's next - LiteStep Professional Edition, for the Home Office?
Expect biannual service packs that will gradually delete every key in your registry.