My current thinking is that it probably makes sense to drop support for MW older than 1.35 on master / for SMW 4.0. Given limited volunteer time to deal with MW 1.35 issues (*), 1.35 being an LTS and little in the way of feature development happening in SMW at the moment, this seems like a good deal. It is what I am doing for Maps.
(*) Dealing with those issues is easier if you do not need to stay compatible with older versions
@kghbln
We just have to make sure that both releases overlap for the support of the latest LTS of MW, i.e. 1.35. Since both 3.2 and 4.0 will support 1.35 I have no objections. Probably we should still do MW 1.34 since this is currently supported though this depends on when we do the 4.0 release.
Probably we should still do MW 1.34 since this is currently supported though this depends on when we do the 4.0 release.
The way I look at things this actually does not make sense. If we release in a year and don't support 1.34, or release now and don't support it, either way, people using 1.34 are not affected. What is different is that people using 1.35 get a new release sooner. Having a release optimized for 1.35 soon is additive. It does not take away from the recent 3.2 release. You could think of it as a 1.35 optimized version of SMW 3.2.
Most helpful comment
My current thinking is that it probably makes sense to drop support for MW older than 1.35 on master / for SMW 4.0. Given limited volunteer time to deal with MW 1.35 issues (*), 1.35 being an LTS and little in the way of feature development happening in SMW at the moment, this seems like a good deal. It is what I am doing for Maps.
(*) Dealing with those issues is easier if you do not need to stay compatible with older versions
@kghbln