Markus - are you suggesting retroactively referring to, say, version 1.5.1 as version 5.1 - with a corresponding change to all the documentation, etc.? Or just jumping straight from version 1.9 to version 10.0? I'm assuming the latter, but in either case that seems like a bad idea, that will in fact cause confusion, without any obvious benefit.

Yes, Java did it, but, as Wikipedia notes [1], that was strictly for marketing purposes, presumably because "Java 6" looks a lot nicer on a book cover than "Java 1.6". Behind the scenes, Java developers still refer to it as 1.6, etc. When the first "SMW Unleashed" book comes out, then maybe it makes sense to start talking about making the number look nicer. :)

I think it's overly dramatic to say that SMW versioning will never move past 1.x. There are a few previous versions that could have merited a jump to 2.0, in my opinion - the most recent two, 1.8 and 1.9, being obvious candidates. Perhaps it was a mistake to not make the major number jump with either of them. (And by the way, maybe it's not too late to rename 1.9 to 2.0? It's only been out for two weeks now...) But trying to pretend that those *were* major version number changes seems like it would cause more problems than it's worth.

Jeroen - the numbering decisions of the developers of core MediaWiki seem irrelevant to this discussion, I would think.



On Fri, Jan 17, 2014 at 8:59 AM, Jeroen De Dauw <jeroendedauw@gmail.com> wrote:

> Markus:
> the next version should be 10.0.0

Good point. +1 to this.

> Alexander:

> It is also important to tag all extensions. This is very often not the case yet...

At least for SMW you can be sure all future releases will be tagged, since Composer essentially requires one to tag in order to create a release. The same is also true for SRF and Maps, and I hope more extensions will follow.

> Yaron:
> I can't imagine anyone would object to increasing the version number to 2.0, 3.0 etc. if/when it makes sense to do that.

A discussion about the same question occurred quite some time back on wikitech. As you can probably guess, the outcome was rather different.


Jeroen De Dauw
Don't panic. Don't be evil. ~=[,,_,,]:3

CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
Semediawiki-devel mailing list

WikiWorks MediaWiki Consulting http://wikiworks.com