Re: [Python-Dev] Arlington VA sprint on Sept. 23
Fred L. Drake, Jr. wrote: I can guess at Martin's thinking, but I'd rather let him speak for himself, since I'm not a trained channeller. ;-) Essentially, I want to give patches more attention, since they are larger contributions. I don't care if bug reports get unnoticed for years; I do worry if patches get unnoticed/unprocessed for years. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Arlington VA sprint on Sept. 23
Martin v. Löwis wrote: Fred L. Drake, Jr. wrote: I can guess at Martin's thinking, but I'd rather let him speak for himself, since I'm not a trained channeller. ;-) Essentially, I want to give patches more attention, since they are larger contributions. I don't care if bug reports get unnoticed for years; I do worry if patches get unnoticed/unprocessed for years. Then a has-patch flag would be okay, wouldn't it, along with assigning a higher priority? Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Arlington VA sprint on Sept. 23
Georg Brandl wrote: I can guess at Martin's thinking, but I'd rather let him speak for himself, since I'm not a trained channeller. ;-) Essentially, I want to give patches more attention, since they are larger contributions. I don't care if bug reports get unnoticed for years; I do worry if patches get unnoticed/unprocessed for years. Then a has-patch flag would be okay, wouldn't it, along with assigning a higher priority? Sure, that would work as well. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Arlington VA sprint on Sept. 23
On Monday 14 August 2006 18:21, Georg Brandl wrote: * flag RFE patches as RFE (patch shouldn't be a category on its own) This is something Martin and I have disagreed over in the past. Martin has indicated that he'd rather see the patches as separate artifacts rather than as attachments to a bug report, while I'd rather see them attached to the relevant bug report or feature request. My thought is that it's easier to deal with fewer items in the tracker. Keeping the candidate patches with the bug report or feature request makes them readily accessible to a reviewer. It's not the only way. I can guess at Martin's thinking, but I'd rather let him speak for himself, since I'm not a trained channeller. ;-) -Fred -- Fred L. Drake, Jr. fdrake at acm.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Arlington VA sprint on Sept. 23
On Tue, Aug 15, 2006 at 12:21:34AM +0200, Georg Brandl wrote: * close RFEs and patches which have no chance of going in (there are many patches on SF having one or two -1 comments, is anyone ever going to check them in without a python-dev discussion?) In the past, someone (I think Raymond) has argued that we shouldn't close old bug reports because even if no one is interested in processing them *now*, someone might come along someday who wants to update that module and fix those bugs or apply those enhancements. Perhaps we need a 'not dead, not actively pursued' state for patches and RFEs. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Arlington VA sprint on Sept. 23
A.M. Kuchling wrote: On Tue, Aug 15, 2006 at 12:21:34AM +0200, Georg Brandl wrote: * close RFEs and patches which have no chance of going in (there are many patches on SF having one or two -1 comments, is anyone ever going to check them in without a python-dev discussion?) In the past, someone (I think Raymond) has argued that we shouldn't close old bug reports because even if no one is interested in processing them *now*, someone might come along someday who wants to update that module and fix those bugs or apply those enhancements. Perhaps we need a 'not dead, not actively pursued' state for patches and RFEs. Open with priority 0? Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
