[Mailman-Developers] Getting to Mailman 3.0 final

[Franck Martin]

Unfortunately, I did not have time to look at porting the optional authorship settings from the branch I did on mailman 2.1 to 3.0. I suppose this is too late to make the 3.0 deadline, but from what I saw of the 3.0 code, this does not seem a complicated change.

How can I register a bug, so that this change can be considered for 3.1?

https://code.launchpad.net/~mlm-author/mailman/2.1-author

Thanks.

----- Original Message -----
From: "Barry Warsaw" <barry at list.org>
To: mailman-developers at python.org
Sent: Monday, September 10, 2012 11:04:59 AM
Subject: [Mailman-Developers] Getting to Mailman 3.0 final

Hi Mailman developers,

I really want to get Mailman 3.0 final out in the next month or so, absolutely
definitely by the end of 2012.  Clearly, the core won't have everything that
everyone wants but I think it will have quite a bit, and be a useful release
for people to start using in production.

In some ways, I view Mailman 3.0 in the same light as Python 3.0.  It was
critical for that version to be released because the reality is that most
people won't test even a beta release.  However, once Python 3.1 was released,
we stopped recommending and maintaining Python 3.0 and just encouraged
everyone to upgrade.

My biggest priority is to ensure that Mailman 3.0 is usable even without a web
ui, and that major projects such as Postorius and HyperKitty can continue
making good progress toward their own releases with 3.0.

To make it easier for me to understand your priorities and needs, I request
that anything you think is missing in Mailman 3 today be added as a bug in our
tracker: <http://bugs.launchpad.net/mailman>.  You must add the 'mailman3' tag
to the bug and bump the importance up to Critical.  In a week or so, I'll
start triaging the bugs and make my own assessments, and then anything marked
critical will be fixed before the final release.  There will be no High bugs,
and everything else will be marked Low and postponed to Mailman 3.1.

In the bug comments, please add justifications or other information you think
will be useful to me while doing a final triage.  Of course, priority always
goes to those bugs that have branches and merge proposals attached to them
(i.e. contributions welcome!).

Cheers,
-Barry