M2Crypto 0.16 mini-roadmap proposal

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.

-- 
  Heikki Toivonen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD8Rkeb8x8KoP+JuwRAlniAKCW9xFRNYQOIbrFOXT+6Il8F8gTkQCgtrSs
6Sib+tHwT2SpMx6QzVeqWe0=
=MMsE
-----END PGP SIGNATURE-----