|
Size: 1038
Comment: Removed unnecessary parens.
|
Size: 1303
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| I would prefer to be working on Mailman 3, but Mailman 2.1 is still what most people are using, and it still needs to be supported. |
Mailman 2.1 is end of life. Going forward there will only be i18n updates and fixes for significant bugs and security issues. |
| Line 17: | Line 16: |
| [[http://mail.python.org/mailman/listinfo/mailman-users|subscribe]] before posting there. | [[http://mail.python.org/mailman3/lists/mailman-users.python.org/|subscribe]] before posting there. You can find Mailman 3 support via the <<MailTo(mailman-users AT SPAMFREE mailman3 DOT org)>> list. You need to [[http://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/|subscribe]] before posting there. |
| Line 23: | Line 25: |
| Aug 5 - 16, 2016 Away with no online access. |
August 15 - September 11, 2022 Away with no online or phone access except Aug 27 - 29 |
Mark Sapiro
Email: <mark AT SPAMFREE msapiro DOT net>
I am a mailman developer. I am the release manager and close to the sole maintainer of the Mailman 2.1 branch. Mailman 2.1 is end of life. Going forward there will only be i18n updates and fixes for significant bugs and security issues.
You can find Mailman 2.1 support via the <mailman-users AT SPAMFREE python DOT org> list. You need to subscribe before posting there.
You can find Mailman 3 support via the <mailman-users AT SPAMFREE mailman3 DOT org> list. You need to subscribe before posting there.
I am occasionally off line for periods of up to two weeks at a time because I like to hike in the back country in the Sierra Nevada and elsewhere.
Schedule:
- August 15 - September 11, 2022
- Away with no online or phone access except Aug 27 - 29