Notifications for bug reports and patches
Currently the SourceForge bug and patch trackers for the Mailman project are set to send messages to mailman-cabal@python.org, which reaches just the core developers (of which I think I'm the only person currently not .forwarding to /dev/null ;).
I'm wondering if it would be useful to redirect those messages to mailman-developers. It would certainly be helpful for me, because it would give you guys a chance to be notified of new bugs or patches, and comment on them via the trackers. This works well in the Python community, and I could certainly use other opinions on a number of bugs and patches.
I don't think it would innundate you all with too much traffic.
Thoughts? I'd probably turn this on after I finish my current bug triage pass.
-Barry
"BAW" == Barry A Warsaw <barry@zope.com> writes:
BAW> Currently the SourceForge bug and patch trackers for the
BAW> Mailman project are set to send messages to
BAW> mailman-cabal@python.org
BAW> I'm wondering if it would be useful to redirect those
BAW> messages to mailman-developers.XEmacs did this when we realized (wea maxima culpa) that _everybody_ had the bugtrack messages redirected to /dev/null.
It's not really optimal, but we didn't get any complaints that I can remember. The non-developer beta testers don't seem to mind either, the few comments I've seen seem to agree that hearing about bugs and crashes, even for "ancient" versions, is preferable to missing even a few current or possibly still current bugs. I wasn't postmaster then so I can't say whether we got any unsubs.
-- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py
participants (2)
-
barry＠zope.com -
Stephen J. Turnbull