Hi,
today is bug day and I've been hacking away on the nightly test result
aggregator script a bit to make the output more readable for the large
number of results we get every night.
Also, I'll be around for the 3pm UTC IRC meeting today.
Christian
--
Christian Theune · c...@gocept.com
Hi,
On 11/30/2010 02:43 PM, Christian Theune wrote:
Hi,
today is bug day and I've been hacking away on the nightly test result
aggregator script a bit to make the output more readable for the large
number of results we get every night.
Also, I'll be around for the 3pm UTC IRC meeting
Am 30.11.2010, 16:47 Uhr, schrieb Christian Theune c...@gocept.com:
However, I'm looking forward to a two-week holiday, so I won't be
present at the meetings next week and the week after. I'll be back at
the meeting on 2010-12-21, though.
I should be able to sit in for the next two meetings
Hi,
the Doodle has spoken: our next bug day will be on 2010-11-30 as 3 out
of 4 people have time there.
So again to everybody: I'd like to invite you to join us fixing bugs in
the general area of Zope (2, ZTK, grok, whatever). If you can spare some
time, please join us.
We'll hang out on
This being PloneConf week, it's not surprising the attendance was even
lower than usual.
On Wed, Oct 27, 2010 at 08:55, Christian Theune c...@gocept.com wrote:
Hi,
On 10/26/2010 09:14 AM, Christian Theune wrote:
[...]
This week my job of summarizing is suprisingly easy: nothing to
Hi,
On 10/26/2010 09:14 AM, Christian Theune wrote:
Hi,
Today is a bug day and the weekly developer meeting.
I haven't managed to write up the log from last week, but basically Jim,
me, and some others talked about about the need for being able to
communicate/document architecture/design
Hi,
Today is a bug day and the weekly developer meeting.
I haven't managed to write up the log from last week, but basically Jim,
me, and some others talked about about the need for being able to
communicate/document architecture/design decisions well - we didn't find
the grand solution,
Am 19.10.2010, 18:42 Uhr, schrieb Christian Theune c...@gocept.com:
another bug day! I've picked next Tuesday based on the input from the
Doodle (Charlie and me) and the IRC (Tres).
For family reasons my time is limited tomorrow but I'll put as much time
into this as possible. There are a
Hi,
another bug day! I've picked next Tuesday based on the input from the
Doodle (Charlie and me) and the IRC (Tres).
So, if you'd like something to get improved: please join us.
Remember: you don't have to join the whole day - fixing a bug is always
helpful and you'll be more likely to be
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
Am 24.08.2010 um 17:12 schrieb Christian Theune:
Hi everyone,
last week was a bug day and I'd like to repeat the exercise from last
time: it would be nice if everyone who was involved in some way to speak
up and say what they worked on.
Hi,
I did the following:
- wrote a blueprint:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked on the following bugs:
Already fixed
=
https://bugs.launchpad.net/products.zsqlmethods/+bug/440993
Fixed
=
https://bugs.launchpad.net/products.zsqlmethods/+bug/142689
Hi everyone,
last week was a bug day and I'd like to repeat the exercise from last
time: it would be nice if everyone who was involved in some way to speak
up and say what they worked on.
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh co. kg · forsterstraße 29 · 06112 halle
-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
Hi,
as doodled, there's a bug day coming up tomorrow. That means reporting,
triaging, fixing, and discussing bugs of Zope 2, Bluebream, grok, ZTK,
just everything touching Zope code to have a shared experience.
If you want to join, we'll hang out on #z...@freenode and me (Theuni,
I'll be
This next Friday (25th) is the last friday of the month. Are we going to
have a bugday?
Cheers, Leo
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Leonardo Rochael Almeida wrote:
This next Friday (25th) is the last friday of the month. Are we going to
have a bugday?
Yes, sorry, I've been slack announcing it, but just done now...
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
On Mon, May 31, 2004 at 10:55:22PM +0200, PieterB wrote:
RESOLVED: #1213, #852, #1293, #1355, #1265, #1352, #1094, #993, #1132,
#596
Thanks for resolving some of the Zope bugs!
It noticed http://collector.zope.org/Zope/1265 is still 'Pending'
according to the collector.
I can change the
It's resolved
--On Dienstag, 1. Juni 2004 9:54 Uhr -0400 Paul Winkler
[EMAIL PROTECTED] wrote:
On Mon, May 31, 2004 at 10:55:22PM +0200, PieterB wrote:
RESOLVED: #1213, #852, #1293, #1355, #1265, #1352, #1094, #993,
#1132,
# 596
Thanks for resolving some of the Zope bugs!
It noticed
Ken Manheimer wrote:
Just a quick status report on today's Bug Day...
10 bugs resolved, 5 set to won't fix, 4 rejected.
RESOLVED: #1213, #852, #1293, #1355, #1265, #1352, #1094, #993, #1132, #596
WONTFIXED: #1193, #329, #1098, #1045, #981
REJECTED: #639, #1238, #489, #1297
Thanks to Paul for
On Mon, May 31, 2004 at 12:37:51PM +0100, Chris Withers wrote:
RESOLVED: #1213, #852, #1293, #1355, #1265, #1352, #1094, #993, #1132,
#596
Thanks for resolving some of the Zope bugs!
It noticed http://collector.zope.org/Zope/1265 is still 'Pending'
according to the collector.
Pieter
[This was mistaken for spam by our filter, and i was too quick to confirm
it as spam...]
-- Forwarded message --
Date: Fri, 28 May 2004 18:02:50 -0400
From: Paul Winkler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug Day status report
Just a quick status report on today's
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,
Just a reminder that bug day is on today. Meet us over on the #zope-dev
channel of irc.zope.org if you can!
-Casey
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
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,
Hi all -
We had been planning to make a Zope 2.7a1 release on Friday,
and another 2.6.2 beta soon as well. Someone noted (rightly!)
that it would be ideal if we could have a bugday first.
So I'll propose next Tuesday the 16th be bug day, and we'll
plan to make both releases by the end of
Brian Lloyd wrote:
Hi all -
We had been planning to make a Zope 2.7a1 release on Friday,
and another 2.6.2 beta soon as well. Someone noted (rightly!)
that it would be ideal if we could have a bugday first.
So I'll propose next Tuesday the 16th be bug day, and we'll
plan to make both
hopefully it will be a tad more successful than the last one
--
Jamie Heilman http://audible.transient.net/~jamie/
You came all this way, without saying squat, and now you're trying
to tell me a '56 Chevy can beat a '47 Buick in a dead quarter mile?
I liked you better when
Just wanted to thank everyone for their participation on bug day and wanted to
followup with a couple of reminders:
1. Make sure CHANGES.txt got updated on the 2.6 branch if you checked in a
change. Its not too late to update it now.
2. Make sure bug fixes you made on the 2.6 branch get merged
I would like to announce a Zope 2 Bug Day for Monday Dec. 16, starting
at 8:00am US Eastern Standard Time.
We will be fixing bugs in preparation for the Zope 2.6.1 release.
What is a Bug Day? A Bug Day is a day dedicated to squashing bugs
lodged in the Zope2 collector at
On Thursday 05 December 2002 5:14 pm, Chris McDonough wrote:
Developers and any other interested parties should gather via IRC on the
#zope-dev channel on irc.openprojects.net at the time and date above.
I think its worth saying that the most important (IMO) outcome from the last
two bugs
On Thu, 5 Dec 2002 21:33:19 +
Toby Dickenson [EMAIL PROTECTED] wrote:
Developers and any other interested parties should gather via IRC on the
#zope-dev channel on irc.openprojects.net at the time and date above.
I think its worth saying that the most important (IMO) outcome from the
Adrian Hungate wrote:
Yeah! Of course, I forgot it was a bug day, and I saw the collector
mailbombing me - I was about to file a bug report on it, I couldn't believe
that much activity was genuine! :)
Well, there were a lot of 'rejected' issues and a fair few deferals too. I'm
mildly
On Fri, Aug 16, 2002 at 09:58:38AM +0100, Chris Withers wrote:
Well, there were a lot of 'rejected' issues and a fair few deferals too.
I'm mildly concerned about some of those rejections being premature and
some of the deferals being used just to bury stuff 'cos no-one has time to
deal
Matt Behrens writes:
Zope Bug Day August 2002 was an unqualified success, with our largest
bug total squashed to date: 45! The number of still-open collector
issues dropped by almost 25%. Thanks to all those who participated!
...
I want to note that I am *very* pleased with recent
From: Dieter Maurer [EMAIL PROTECTED]
Matt Behrens writes:
Zope Bug Day August 2002 was an unqualified success, with our largest
bug total squashed to date: 45! The number of still-open collector
issues dropped by almost 25%. Thanks to all those who participated!
...
I want to
Zope Bug Day August 2002 was an unqualified success, with our largest
bug total squashed to date: 45! The number of still-open collector
issues dropped by almost 25%. Thanks to all those who participated!
More information on Zope Bug Days can be found at
http://dev.zope.org/CVS/BugDays. I
Hi Folks,
We'd like to schedule a Bug Day for this upcoming Wednesday. A Bug
Day is a day that we set aside to try to pay attention to unfixed bugs
that have found their way into the Collector at
http://collector.zope.org . Anyone who is capable and willing to
participate in these
I just wanted to give a quick summary of Bug Day June 2002, and get
people thinking about July 2002 a little sooner so maybe more people can
make it. Yeah, I know there were a lot of things going on this time
around...
Anyway, we fixed #151, #72, #6, #402, #79, #272, #409, #312, and #432,
Brian Lloyd [EMAIL PROTECTED] wrote:
Are we having a Bug Day on Friday?
I'd prefer if we could have Bug Days on Thursdays instead of Fridays.
Friday means I have to stay late at work when the weekend has already
started and everybody else is at the pub/café/parties :-)
Same
Are we having a Bug Day on Friday?
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
Are we having a Bug Day on Friday?
I'd prefer if we could have Bug Days on Thursdays instead of Fridays.
Friday means I have to stay late at work when the weekend has already
started and everybody else is at the pub/café/parties :-)
Same thing for all of us Europeans I guess.
Florent
--
On Tue, 2002-06-11 at 15:22, Florent Guillaume wrote:
Are we having a Bug Day on Friday?
I'd prefer if we could have Bug Days on Thursdays instead of Fridays.
+1
--
Ideas don't stay in some minds very long because they don't like
solitary confinement.
Are we having a Bug Day on Friday?
I'd prefer if we could have Bug Days on Thursdays instead of Fridays.
Friday means I have to stay late at work when the weekend has already
started and everybody else is at the pub/café/parties :-)
Same thing for all of us Europeans I guess.
How about
60 matches
Mail list logo
