Foofy Versioning
All these years, I’d hoped that WordPress would start versioning like Mozilla did: point releases, with major milestones getting a first-digit change. Instead, WP went from 0.72 to [I believe] 1.0, then to 1.2 [with a couple minor revs], then to 1.5 [with all the silly revs since then].
Now, Mozilla will version like WordPress. Why not just generate version numbers with a random number generator, and only accept the random result if it’s higher than the last number you had? John Wilson could code up such a script in 35 seconds, and Gareth Watts could have a version outputting for all SourceForge projects in a half-day, tops.
Le sigh.
Don’t blame me. Matt does his own thing when it comes to version numbers for WP.
However, I wouldn’t call the 1.5.x revs “silly”, since there are important security fixes in there
Maybe we should do away with numeric versions, and strictly use codenames. “I forgot, what’s the newest WordPress release? Is it ‘Wombat’ or ‘ToeJam’?”
July 26th, 2005 at 10:27Well, I would’ve just called it 1.5.2, 1.5.3, etc. No doubt they’re important fixes, though.
And Matt already does his jazz-named releases. I’m still patiently waiting for Brubeck.
July 26th, 2005 at 10:44