[Mailman-Developers] Important Mailman 2.1.9 to 2.1.10 upgradenote.
barry at python.org
Wed Apr 23 22:32:09 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
On Apr 22, 2008, at 2:44 PM, Mark Sapiro wrote:
> Bob Puff at NLE wrote:
>> +1 on the auto-delete. I have a lot of boxes running Mailman that
>> I periodically have to go into to
>> clean out stuff, and having more junk pile up, while helpful for
>> debugging, isn't great for production.
>> David Lee wrote:
>>> If this is deemed "Important" (for anyone upgrading over the next
>>> year or
>>> more), and if this cleaning process is well-defined and capable of
>>> mechanisation, then might it be worth superseding 2.1.10 with a
>>> (or 2.1.11 or whatever nomeclature is appropriate) that
>>> automatically does
>>> this cleaning?
> I think this is a good idea. If I had remembered about the unparseable
> .bak files, and thought it through, I could have added code to
> bin/update to remove them, and I still can for a fix-up release.
> Also, In another thread, Barry asked for feedback on "some kind of
> shunt queue culler cron script". I think this is a good idea, either
> for a separate cron, or incorporated into one of the existing crons.
> How about something like a couple of Default config settings like
> BAD_SHUNT_ARCHIVE_DIRECTORY = None
> BAD_SHUNT_STALE_AFTER = days(7)
> With the idea being anything in the 'bad' or 'shunt' queues older than
> BAD_SHUNT_STALE_AFTER would be discarded or moved to
> BAD_SHUNT_ARCHIVE_DIRECTORY if it existed.
> Do people like this idea?
+1, but I think it should be a separate cron script. Keep 'em small
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
More information about the Mailman-Developers