Public bug reported:
It looks like there is no way for a MM3 plugin to be signaled for a new
posting.
It would be great if core could provide a notification to the plugins
that have subscribed to this event when a new post occurs.
This notification should carry some interesting information, like the
number of recipients and the message size.
This request is also essential for the MM3-Metrics module
(https://launchpad.net/mm3-metrics).
** Affects: mailman
Importance: Undecided
Status: New
** Tags: events mailman3 metrics modules notification plugins post
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1094696
Title:
Event notifications on postings
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1094696/+subscriptions
Public bug reported:
Mailman Core and Postorius have sets of tests, but could use more
extensive test coverage. This bug is meant to be a repeatable bug
suitable for new contributors (e.g. prospective Google Summer of Code
Students). In short: find a piece of Postorius or Mailman Core that
isn't yet tested and write a test (or set of tests) for it.
Contributors wishing to work on Mailman Core should look at START.rst
and DATABASE.rst for more information about setting up tests.
For Postorius, Florian is working on vcrpy test integration, so new
tests can use that format.
Links to documentation and examples much appreciated to update this bug!
** Affects: mailman
Importance: Undecided
Status: New
** Affects: postorius
Importance: Undecided
Status: New
** Tags: beginner-friendly easy mailman3 repeatable test
** Tags added: easy mailman3
** Also affects: mailman
Importance: Undecided
Status: New
** Description changed:
- Postorius has a set of tests, but it could use more extensive coverage.
- This bug is meant to be a repeatable bug suitable for new contributors
- (e.g. prospective Google Summer of Code Students). In short: find a
- piece of postorius that isn't yet tested and write a test (or set of
- tests) for it.
+ Mailman Core and Postorius have sets of tests, but could use more
+ extensive test coverage. This bug is meant to be a repeatable bug
+ suitable for new contributors (e.g. prospective Google Summer of Code
+ Students). In short: find a piece of Postorius or Mailman Core that
+ isn't yet tested and write a test (or set of tests) for it.
- Florian is working on vcrpy test integration, so new tests can use that
- format.
+ Contributors wishing to work on Mailman Core should look at START.rst
+ and DATABASE.rst for more information about setting up tests.
+
+ For Postorius, Florian is working on vcrpy test integration, so new
+ tests can use that format.
+
+ Links to documentation and examples much appreciated to update this bug!
** Tags added: repeatable
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1414352
Title:
Improve code coverage by adding tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1414352/+subscriptions
Public bug reported:
In Ubuntu 16.04 LTS the version of Mailman currently available in the
package manager is 2.1.20 while the latest one is 2.1.29 and which is
also the latest available on Mailman website.
There has been several bug and security fixes since 2.1.20 to 2.1.29
which look interesting to get the package managed upgraded.
What it takes to get the package bumped to 2.1.29 in Ubuntu 16.04 ?
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1803838
Title:
Mailman Upgrade to 2.1.29 - Ubuntu 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1803838/+subscriptions
