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.
Charlie
--
Charlie Clark
Managing Director
Clark Consulting Research
German Office
-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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on Zope2 bugs today. This is what I managed to get done:
Fixed
=
- https://bugs.launchpad.net/zope2/+bug/143273
- https://bugs.launchpad.net/zope2/+bug/143564
- https://bugs.launchpad.net/zope2/+bug/143722
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried to work on fixing the zope.testing tests under Zope 2.7:
https://bugs.launchpad.net/zope.testing/+bug/605455
I did fix the zope.testing buildout to get its own tests passing under
Zope 2.6, and added an optional 'test27' part for running
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 ran
-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 I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, I was able to fix two bugs in zope.testrunner:
. zope.testrunner 4.0.0b2 uninstallable when using Python 2.4,
https://bugs.launchpad.net/bugs/595052
- - StartUpFailure.shortDescription() fails with AttributeError,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on Zope2 bugs today. This is what I managed to get done:
Fixed
=
https://bugs.launchpad.net/zope2/+bug/143946
https://bugs.launchpad.net/zope2/+bug/374818
https://bugs.launchpad.net/zope2/+bug/142535
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
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
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 then,
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
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
--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
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:
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,#666,
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:
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,
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,#666,
20 matches
Mail list logo
