On 10/05/11 23:31, Jeroen De Dauw wrote:
Hey,
Trust me, I've learned to leave SMW alone, lest I get eaten by you and
Yaron.
Help is welcome, but please be aware of what we are trying to do, so you don't end up doing counter-productive work. I think this is a quite reasonable request, true for open source projects in general.
Long live MW 1.12!
Such as for example that for SMW and many of it's extensions, the current oldest MW that should be supported is 1.15.
As I remember, the b/c debate came up a few months back here, and it was agreed upon that b/c code should not be removed unless there is good reason for it, esp in extensions, and even more so in extensions actively maintained. I'm posting here specially to avoid any mishap, so it'd be nice if you'd appreciate this and not throw around rediculous claims about the b/c policy set by people for extensions they wrote and they maintain in their free time, with the implied argument that you know better. (At least this is how it comes over to me.)
I agree with these concerns, but let us not argue too much about this. Overall, our goals should be almost the same. SMW has some inertia to stay with its users who are slow on upgrading, but we are committed to move with MW and support its most recent versions at all times. When we do b/c code, then we always try to make it so that special code is used only for old MWs, and to take advantage of new MW features as the default. It is often difficult to ensure that the most modern MW API is used in all applicable places. Help is very welcome, as long as the backwards compatibility as claimed in INSTALL is preserved (currently MW 15.4).
Cheers,
Markus