A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-March/020688.html below:

[Python-Dev] Moving bugs and patches through the pipeline more quickly

[Python-Dev] Moving bugs and patches through the pipeline more quickly [Python-Dev] Moving bugs and patches through the pipeline more quicklyMartin v. Loewis martin@v.loewis.de
07 Mar 2002 08:09:08 +0100
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



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4