Hi,
I would make a CPAN release of 0.99 of the current code base without
further changes. This should support back to 2.5.3 I think.
Branch SVN with a label wxWidgets-2.6
Announce that version 1.00 will only support 2.8 +
Announce that active 2.8 support will be dropped when 3.2 is released or
12 months after the 3.0 release, whichever is later.
When you stop actively incorporating 2.8 fixes, branch SVN with a label
wxWidgets-2.8
Anyone with an interest in maintaining support for 2.6 and then 2.8 can
form a community to share the work of backporting any enhancements or
fixes to 2.6 / 2.8 as they wish. You can direct your efforts to
incorporating latest features rather than compatibility.
Such communities could maintain a latest dist download at the
sourceforge site and you could add a note to the website and pod on
where to get possibly supported legacy versions.
I think it is unreasonable to expect you to maintain the current level
of backward compatibility. The above scheme means that if I have code
that is 2.8 reliant, I have an idea of how long I've got to convert it
to 3.x.
If I really want to stick with 2.8, you've made it as easy as you can
for me to do so and share in the work from everyone else who wishes to
maintain 2.8 support.
The key point for me is that if you pre-announce the end of 2.8 support
as a 2.8 user I'm pushed to do something about it and you don't have to
maintain backwards compatibility for as long as you have 2.6
I say this as someone who expects to have a reliance on 2.8 well beyond
the proposed 'official' end of life. I'll just have to put in my own
effort rather than relying on yours.
That's my opinion :-)
Regards
Mark
On 13/03/2011 09:47, Mattia Barbon wrote:
Hi,
current wxPerl releases should support wxWidgets versions as far back as
2.5.3 (the version that has been included in OS X Tiger).
I don't think there is any need to maintain compatibility with 2.5.3 and
2.6.x for newer releases; what do others think?
Regards,
Mattia
