[Python-Dev] Moving bugs and patches through the pipeline more quickly (original) (raw)
Guido van Rossum guido@python.org
Thu, 07 Mar 2002 20:41:35 -0500
- 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 ]
Someone who is green like me needs the guidance and the mentoring and the counsel, and the occasional slap on the wrist.
I hope other python-dev'ers can help you find your way.
There is a patch that has been unlooked at. It was discussed on c.l.py., some people decided it was a bug, and I was told to make a patch and put it on SF. I did. It has been almost two months now, and there has been no response.
It would have been better to ask about the fate of that bug on python-dev rather than submit a meta-bug report. :-)
#502080 - BaseHTTPServer senderror bug fix https://sourceforge.net/tracker/?func=detail&aid=502080&groupid=5470&atid=305470
Hm, that one must've fallen between the cracks. I've approved it and assigned it to Skip for commitment.
And so I was under the impression that the real bugs weren't handled at sourceforge, that they were handled somewhere else on some secret mailing list or some other older dev site in Pythonlabs. I thought only a few eyes were watching. I thought that it really didn't matter that much, and so I played games with it.
So now you know the truth. :-)
Keep at it though, and you'll be a release manager before you know it. :-)
--Guido van Rossum (home page: http://www.python.org/~guido/)
- 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 ]