Re: [Zope-dev] Bug day report

2010-10-01 Thread Marius Gedminas
On Fri, Oct 01, 2010 at 10:22:13AM +0200, Charlie Clark wrote: > I'll admit to spending most of my time on new CMF stuff but I did close > two bugs that I felt comfortable with. Didn't seem anyone else was hanging > around on IRC with bugfixing on their mind. I saw your checkins (and mentally

Re: [Zope-dev] Bug day report

2010-10-01 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/1/10 10:22 , Charlie Clark wrote: > Hi, > > I'll admit to spending most of my time on new CMF stuff but I did close > two bugs that I felt comfortable with. Didn't seem anyone else was hanging > around on IRC with bugfixing on their mind. I

Re: [Zope-dev] Bug day report

2010-06-19 Thread Roman Joost
On Fri, Jun 18, 2010 at 11:07:15AM -0400, Tres Seaver wrote: > Roman Joost wrote: > > Thank you. I actually had troubles running all tests in zope.testrunner. > > I need to check why to be sure, to avoid commiting something broken. > > Marius fixed the buildout for that. It was actually my bad - I

Re: [Zope-dev] Bug day report

2010-06-18 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roman Joost wrote: > On Thu, Jun 17, 2010 at 07:59:18AM -0400, Tres Seaver wrote: >> Roman, I landed my version of the fix in 'zope.testrunner', but didn't >> touch it in 'zope.testing', since you were working on it. I was rushing >> a little because

Re: [Zope-dev] Bug day report

2010-06-17 Thread Roman Joost
Hi Tres, On Thu, Jun 17, 2010 at 07:59:18AM -0400, Tres Seaver wrote: > Roman, I landed my version of the fix in 'zope.testrunner', but didn't > touch it in 'zope.testing', since you were working on it. I was rushing > a little because I wanted to release 'zope.testrunner', but wanted to > check

Re: [Zope-dev] Bug day report

2004-05-07 Thread Chris Withers
Casey Duncan wrote: I will try to tread a little lighter on the Reject button and add a comment requesting clarification regardless of age. If I don't hear any for a month or so, then the bug will be closed. Great, don't suppose you can do a mind-meld with Andreas and Maik and get that point acros

Re: [Zope-dev] Bug day report

2004-05-06 Thread Casey Duncan
On Thu, 6 May 2004 10:45:03 -0400 "Tim Peters" <[EMAIL PROTECTED]> wrote: [..] > On the Python bug tracker, I don't close vague bug reports instantly. > Instead I add a note, saying that unless more information is added, > the bug will be closed a month later. It's rare that more info gets > added

RE: [Zope-dev] Bug day report

2004-05-06 Thread Tim Peters
[Chris Withers] > I feel compelled to scream "me too!" here. Closing a bug, even if > anonymously or incompletely reported does not make Zope any better. > See the recent case of a bug that was closed that was still an > outstanding crash issue. Thankfully Tim managed to rescue that one. While th

Re: [Zope-dev] Bug day report

2004-05-06 Thread Chris Withers
Dieter Maurer wrote: True. But if they are not planned to be fixed at all, then they should be closed. You risk to get less bug reports in the collector... Filing a (good) bug report takes quite a bit of time. When you have gotten rejections for several bug reports (that took you quite

Re: [Zope-dev] Bug day report

2004-05-01 Thread Dieter Maurer
Lennart Regebro wrote at 2004-4-30 22:21 +0200: >Dieter Maurer wrote: >> Casey Duncan wrote at 2004-4-29 22:19 -0400: >> >>>I'm happy to report a successful bug day with a final tally of almost 40 >>>issues closed. The specific issues we squashed were: >>> >>>#28,#181,#321,#340,#349,#439,#444,#495

Re: [Zope-dev] Bug day report

2004-05-01 Thread Andreas Jung
--On Samstag, 1. Mai 2004 13:13 Uhr +0100 Chris Withers <[EMAIL PROTECTED]> wrote: Lennart Regebro wrote: There are many bugs with ambigous descriptions, or posted anonymously, or things that are rather like support questions than bugs. If I see them I close them. Hard and brutal. :) I agree mo

Re: [Zope-dev] Bug day report

2004-05-01 Thread Chris Withers
Lennart Regebro wrote: There are many bugs with ambigous descriptions, or posted anonymously, or things that are rather like support questions than bugs. If I see them I close them. Hard and brutal. :) This worries me. I think we need a better documented set of circumstances that are used for re

Re: [Zope-dev] Bug day report

2004-05-01 Thread Chris Withers
Casey Duncan wrote: This means it is an unsponsored bug. It should not remain open forever. Urm, I don't really think this logic is sound ;-) The bug collector is not a substitute for documentation and issues that will never be resolved should be closed. Otherwise it wastes the time of volunteer b

Re: [Zope-dev] Bug day report

2004-04-30 Thread Lennart Regebro
Dieter Maurer wrote: Casey Duncan wrote at 2004-4-29 22:19 -0400: I'm happy to report a successful bug day with a final tally of almost 40 issues closed. The specific issues we squashed were: #28,#181,#321,#340,#349,#439,#444,#495,#511,#532,#540,#543, #544,#545,#546,#553,#562,#574,#584,#602,#637,#

Re: [Zope-dev] Bug day report

2004-04-30 Thread Casey Duncan
On Fri, 30 Apr 2004 20:14:30 +0200 Dieter Maurer <[EMAIL PROTECTED]> wrote: > Casey Duncan wrote at 2004-4-29 22:19 -0400: > >I'm happy to report a successful bug day with a final tally of almost > >40 issues closed. The specific issues we squashed were: > > > >#28,#181,#321,#340,#349,#439,#444,#4

Re: [Zope-dev] Bug day report

2004-04-30 Thread Dieter Maurer
Casey Duncan wrote at 2004-4-29 22:19 -0400: >I'm happy to report a successful bug day with a final tally of almost 40 >issues closed. The specific issues we squashed were: > >#28,#181,#321,#340,#349,#439,#444,#495,#511,#532,#540,#543, >#544,#545,#546,#553,#562,#574,#584,#602,#637,#644,#654,#658,#6