[Python-Dev] Moving bugs and patches through the pipeline more quickly (original) (raw)
Martin v. Loewis martin@v.loewis.de
07 Mar 2002 08:09:08 +0100
- Previous message: [Python-Dev] Moving bugs and patches through the pipeline more quickly
- Next message: [Python-Dev] Moving bugs and patches through the pipeline more quickly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Skip Montanaro <skip@pobox.com> writes:
I wasn't thinking about it quite like that. I was thinking more along the lines of a subset of people would volunteer to do the triage, passing it off between themselves at the rotation boundaries. That's more-or-less how Cameron Laird does it for the weekly Python URL stuff.
I quite agree with Guido that no further formal procedure is needed. Those of us that do look into bug reports on a regular basis probably agree: for the new reports, it is easy to see whether there has been any response at all, as reports age, it might be necessary to study an issue in more detail even if there had been responses from your usual suspects.
Well, like most people, I need occasional re-reminding. ;-)
If "occasional" means "once a month": I can setup a cron job to send you a message automatically :-)
Regards, Martin
- Previous message: [Python-Dev] Moving bugs and patches through the pipeline more quickly
- Next message: [Python-Dev] Moving bugs and patches through the pipeline more quickly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]