> Keeping ahead of spammers and trying to work on a 2.6 version, which > has to run on an obsolete version of perl few of the developers have any > experience with, in parallel with the 3.0 version, is even harder.
Which obsolete version of perl does 2.64 require? I'm using 5.8.5 - is that already obsolete?
It's not your version that's obsolete, it's the minimum version that SA 2.6x must run on...
SA 2.64 must run on perl 5.0005 or higher.
SA 3.0 only supports 5.61 and up.
> It's also partly due to licensing differences. SA is now an ASF project, > but SA 2.x has a non-apache license. SA 3.0 code cannot always be > backported to SA 2.x in a trivial manner.
Also fully appreciated. Just in case I were to backport some 3.0 features, can
you point to specific licensing problems I would need to be aware of?
Disclaimer: I am not a lawyer, if you need legal advice, consult a lawyer with full copies of the licenses.
All of SA 3.0 is Apache licensed, SA 2.6x is artistic/GPL dual separable. While AFAIK these two aren't outright incompatible, one license can't subsume the other. Any resulting version would actually have to conform to all of the terms of both the Apache license, and the artistic half of the artistic/GPL dual. (the Apache license is GPL incompatible, so you could not choose the GPL half for the resulting program)
That's probably not a big deal for a general end user, but it might get slightly tricky in terms of redistribution. The Artistic license is a tad odd and tough to follow in places.
