[Mailman-Developers] Getting to Mailman 3.0 final

[Terri Oda]

Oh, hey, this reminds me...

As I've mentioned before, I'm interested in seeing dynamic sublists 
replace topics in Mailman 3.0.  We've got a student working on the port, 
but honestly he's been dragging his heels and I'm starting to doubt it's 
going to be done by the end of September.

What do you think the best timing for new feature-ish things?  I'm 
guessing post-release makes more sense, but if there's a window of 
pre-release time that would make sense for this I might be able to help 
with the push and make sure we get in under the wire. Deadlines are 
always good motivation. ;)

  Terri

On 12-09-10 12:04 PM, Barry Warsaw wrote:
> 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
>
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/terri%40zone12.com
>
> Security Policy: http://wiki.list.org/x/QIA9