Re: M2Crypto 0.16 mini-roadmap proposal

Heikki Toivonen wrote:

I think we should require SWIG version  1.3.24 or newer(The latest 
version 1.3.28). They were a lot of changes
between version 1.3.23 an d 1.3.24, which could make supporting older 
versions difficult.
I've made this a requirement for one of my projects.

I think we should have M2Crypto work with OpenSSL 0.9.7 and newer. We've 
already done
a lot of the work to make M2Crypto to work with 0.9.7 and 0.9.8 
versions. So I think it is worth the
effort and I believe that the cvs code compiles with 0.9.7 and 0.9.8 
versions.

Python 2.3 or newer seems like a reasonable requirement.

Matt Rodriguez

> I think it would be time to start thinking about what the next M2Crypto
> release should look like. There are a few patches with some new features
> that are also waiting for checkins already, and there are some ideas for
> more stuff as well.
>
> Some of the new features that are waiting checkin depend on OpenSSL 0.9.8.
>
> There are also a bunch of cleanup work that could be done if support for
> older Python and SWIG versions were dropped.
>
> Therefore I think M2Crypto 0.16 should require:
>   * OpenSSL 0.9.8 or newer
>   * Python 2.3 or newer
>   * SWIG (not sure what yet)
>
> The 0.15 branch would naturally remain available for older versions of
> those, and if there is demand/need maintenance releases could be made to
> fix security issues and the like.
>
> As for timeline, a release sometime next summer (ideally sooner if
> possible) would be my goal.
>
>