|
Size: 5578
Comment:
|
Size: 6150
Comment: sprint update
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| This is where I am collecting the feature list and other artifacts for Mailman 3.0 which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman functionality through a REST API, architecturally separate components loosing communicating for better system administration and development lifecycles, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go. | We aim to release Mailman 3.0 on Thursday, April 16, 2015. |
| Line 6: | Line 6: |
| There is currently no ETA for Mailman 3, but there have been several beta releases and development is moving quickly. Contributors are welcome and encouraged! Discussions will happen on the [[mailto:mailman-developers@python.org|mailman-developers mailing list]]. Anyone can check out and use the [[../MailmanBranches|current development source branches]]. The TODO list below is not a commitment of features (unless marked with a '''Done''' ). | This page is where we are collecting the feature list and other artifacts for Mailman 3.0, which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman functionality through a REST API, architecturally separate components loosing communicating for better system administration and development lifecycles, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go. Contributors are welcome and encouraged! Discussions will happen on the [[mailto:mailman-developers@python.org|mailman-developers mailing list]]. Anyone can check out and use the [[../MailmanBranches|current development source branches]]. The TODO list below is not a commitment of features (unless marked with a '''Done''' ). |
| Line 18: | Line 20: |
| The suite as a whole is currently [[https://mail.python.org/pipermail/mailman-announce/2014-December/000197.html|at 3.0b5]]. [[https://mail.python.org/pipermail/mailman-developers/2015-January/024147.html|It would be great]] to get a 3.0 release of the suite out during the [[DEV/PyCon 2015 Sprint|PyCon sprints in April 2015]]. | The suite as a whole is currently [[https://mail.python.org/pipermail/mailman-announce/2014-December/000197.html|at 3.0b5]]. [[https://mail.python.org/pipermail/mailman-developers/2015-January/024147.html|We aim]] to get a 3.0 release of the suite out by the end of the [[DEV/PyCon 2015 Sprint|PyCon sprints, April 13-16 2015]]. Mailman 3.0 is most suitable to new installations of Mailman. We do not guarantee that it will work well for migrations and upgrades of Mailman 2.x; we believe that will work, but encourage you to make backups and test your migrations first. It is not yet at full feature parity with Mailman 2.x, but we're working on that for 3.1. |
| Line 33: | Line 37: |
| Here are things we need to do before Mailman 3.0 Suite final can be released. We started this list with the leftovers from [[../PyCon Sprint 2013|PyCon Sprint 2013]] and updated it in mid-January 2015. | == 3.0 == Here are things we need to do before Mailman 3.0 Suite final can be released. We started this list with the leftovers from [[../PyCon Sprint 2013|PyCon Sprint 2013]] and updated it at the [[../PyCon 2015 Sprint|PyCon Sprint 2015]]. |
| Line 36: | Line 42: |
| * --(Update the bundler that packages Mailman 3/Hyperkitty/Postorius together with appropriate setup scripts)-- * Internationalization - there must be a way for the community to contribute translations and for us to integrate them into releases ([[https://bugs.launchpad.net/mailman/+bug/1414154|bug 1414154]]) * Migration scripts for current Mailman 2 installations ([[https://bugs.launchpad.net/mailman/+bug/965532|bug 965532]]) * Mailman 2 & 3 co-existing? * --(Integrate hyperkitty/postorius into a single django install? (nice to have))-- (done by the bundler) |
* Update installation HOWTO(s) * Write release notes and announcement * Test new installs of 3.0 suite |
| Line 44: | Line 48: |
| * --(Add user settings page (Likely to be completed as part of stylistica's summer of code work; may need temporary fix sooner))-- * --(Add ability to add/remove email addresses from a user record (currently waiting on discussions with core about how to do this. Will we need to send email confirmations?))-- * --(Add ability to remove moderators/owners from a list (see [[https://bugs.launchpad.net/postorius/+bug/1062889|bug 1062889]]))-- |
|
| Line 48: | Line 49: |
| * Archival options (just added in mailman.client). | * Archival options (just added in mailman.client, needs to go into Postorius). * Pull list of supported languages for a domain from Mailman core via API (see [[https://bugs.launchpad.net/mailman/+bug/1414298|bug 1414298]]) * Add option to choose address for subscription, if a user has more than one address * Add option to change subscription for a different address after subscription - Abhilash * Hyperkitty * Improve UI around user registration/login/password (see [[https://fedorahosted.org/hyperkitty/ticket/23|bug 23]]) * Websites * Post HOWTO, release notes & announcement == 3.1 == TODOs for the next point release of 3.x: * Mailman Suite: * Internationalization - there must be a way for the community to contribute translations and for us to integrate them into releases ([[https://bugs.launchpad.net/mailman/+bug/1414154|bug 1414154]]) * Migration scripts for current Mailman 2 installations ([[https://bugs.launchpad.net/mailman/+bug/965532|bug 965532]]) * Test migration from 2 to 3 * Mailman 2 & 3 co-existing * Make it easier to install with Docker * Core * Postorius * Implementation of django-browserid + custom audience checking * Add user settings page (Likely to be completed as part of stylistica's summer of code work; may need temporary fix sooner) * Add ability to remove moderators/owners from a list (see [[https://bugs.launchpad.net/postorius/+bug/1062889|bug 1062889]]) |
| Line 50: | Line 73: |
| * --(Implementation of django-browserid)-- + custom audience checking (not critical) * Pull list of supported languages for a domain from Mailman core via API (see [[https://bugs.launchpad.net/mailman/+bug/1414298|bug 1414298]]) |
|
| Line 53: | Line 74: |
| * --(work with Mailman 3 core (including using core API rather than internal interfaces))-- | * if a nonmember replies via the web interface, subscribe them as nondelivery member |
| Line 58: | Line 79: |
Mailman 3.0
We aim to release Mailman 3.0 on Thursday, April 16, 2015.
This page is where we are collecting the feature list and other artifacts for Mailman 3.0, which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman functionality through a REST API, architecturally separate components loosing communicating for better system administration and development lifecycles, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go.
Contributors are welcome and encouraged! Discussions will happen on the mailman-developers mailing list. Anyone can check out and use the current development source branches. The TODO list below is not a commitment of features (unless marked with a Done ).
Development and status
Mailman 3 is essentially five projects:
The suite as a whole is currently at 3.0b5. We aim to get a 3.0 release of the suite out by the end of the PyCon sprints, April 13-16 2015.
Mailman 3.0 is most suitable to new installations of Mailman. We do not guarantee that it will work well for migrations and upgrades of Mailman 2.x; we believe that will work, but encourage you to make backups and test your migrations first. It is not yet at full feature parity with Mailman 2.x, but we're working on that for 3.1.
Developer resources:
To Do List
3.0
Here are things we need to do before Mailman 3.0 Suite final can be released. We started this list with the leftovers from PyCon Sprint 2013 and updated it at the PyCon Sprint 2015.
- Mailman Suite:
- Update installation HOWTO(s)
- Write release notes and announcement
- Test new installs of 3.0 suite
- Core
- Postorius
subscription moderation (see bug 1058449)
- Archival options (just added in mailman.client, needs to go into Postorius).
Pull list of supported languages for a domain from Mailman core via API (see bug 1414298)
- Add option to choose address for subscription, if a user has more than one address
- Add option to change subscription for a different address after subscription - Abhilash
- Hyperkitty
Improve UI around user registration/login/password (see bug 23)
- Websites
Post HOWTO, release notes & announcement
3.1
TODOs for the next point release of 3.x:
- Mailman Suite:
Internationalization - there must be a way for the community to contribute translations and for us to integrate them into releases (bug 1414154)
Migration scripts for current Mailman 2 installations (bug 965532)
- Test migration from 2 to 3
Mailman 2 & 3 co-existing
- Make it easier to install with Docker
- Core
- Postorius
- Implementation of django-browserid + custom audience checking
- Add user settings page (Likely to be completed as part of stylistica's summer of code work; may need temporary fix sooner)
Add ability to remove moderators/owners from a list (see bug 1062889)
non-member disposition [Put list of non-members in list settings with allow/deny, etc] (see bug 1414149)
- Hyperkitty
- if a nonmember replies via the web interface, subscribe them as nondelivery member
- Websites