On Sep 11, 2012, at 05:38 PM, Franck Martin wrote: >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
For now, file the bug as normal, but add the 'mailman3' tag. At some point when I create the 3.1 series and start targeting bugs to that series, I will go through all the mailman3 tagged bugs and evaluate them as either new features (i.e. 3.1) or bug fixes (i.e. for 3.0.x). Also, if you do port the code to lp:mailman, that would be great. You can push the branch and do a merge proposal against lp:mailman, which will always be the currently in-development branch. I'll create a maintenance branch for 3.0.x at some point. Cheers, -Barryu
signature.asc
Description: PGP signature
_______________________________________________ Mailman-Developers mailing list [email protected] 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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
