It was merely a suggestion, one you shot down rather well, I might add, that I included mostly to have some kind of alternative versioning system to discuss. M.m.µ it is! -Carlos

Uh, that sounds confusing to me just reading it... %-) You mean we don't add version numbers to the downloadable archives (like ZIP or tar.bz2) but name them like this: - lifepress-andromeda.zip - lifepress-beteigeuze.zip - lifepress-centauri.zip ... I think that would require a tutorial document for the users about

If we decide to go with named releases we could have them proceed in alphabetical order to limit the high potential for confusion associated with named and un-numbered releases. -Carlos

Personally I like the MAJOR.MINOR.MICRO and it is what I used for a long time. The MICRO is always internal for me, so users only see MAJOR.MINOR as a release. Adding the patch could be useful, but I'm more on the "release often"-side. ;-) Having a speakable name could add to user experience, although I have

And maybe it makes sense that you checkout the current DEV version with language support build in before you start converting your site into a theme. :-) Would be nice to have another theme with full language support, and I think that you'll find some more missing localizations. PLUS you could write a short tutorial about localizing themes or building one from

I don't know how important it is right now to decide how versioning is going to work but I thought I'd bring it up anyway. My proposal is as follows: MAJOR.MINOR.MICRO followed by an optional .PATCHLEVEL and/or -TAG (ie. v1.2.3.4-foo) (This is actually the versioning system that TOR uses and I just happened to like it a lot)