-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[Trimmed CC to just -developers]
On Jan 3, 2009, at 2:51 PM, Mark Sapiro wrote:
Barry has been making wonderful progress with Mailman 3.0 and has just announced the second alpha release.
This may leave some of you wondering what's happening with the Mailman 2.x series, so this note is for all interested Mailman users, developers and translators to give an idea of what to expect in Mailman 2.x in the coming months.
Within the next few days, I plan to release Mailman 2.1.12rc1. This release contains several minor bug fixes since 2.1.11 and is updated for compatibility with Python 2.6. It will not work with Python older than 2.4.
In the absence of "show stopping" bugs, the only changes between this and the final 2.1.12 release will be translation updates. I expect to release the final by the end of January.
After January, my focus will be on Mailman 2.2. This branch was originally intended to be an overhaul of Mailman's GUI, but that work is stalled and will be deferred to Mailman 2.3 or 3.0. The focus of Mailman 2.2 will be ongoing maintenance of the 2.x series and several small new features that have not been added in the 2.1 branch because of i18n considerations.
I hope to be able to release a 2.2 beta before the end of March, 2009.
Mark, thanks for publishing this roadmap. It seems right on target to
me, with one comment. I really hope that there will not be a Mailman
2.3. I agree we'd hoped that 2.2 would include an updated web ui, but
if that won't happen in 2.2, I'd really like to see that effort put
into 3.0. I agree that there are plenty of other good things that can
go into the 2.2 series to make it very much worthwhile, but after that
I think we should concentrate on 3.0, where the backend storage and
other architectural improvements will really pay off.
Cheers,
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkliOToACgkQ2YZpQepbvXG0AACfZcILwdppJDimq8TzRxVfRTxp gFoAoKL2t43LnxawxFIyqaWwGOLWymui =1FuB -----END PGP SIGNATURE-----