[Zope-dev] Bug day and IRC meeting
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 gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day and IRC meeting
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 today. To wrap this up: I've spend a bit of time today revamping the aggregator script (there's drafts floating around now) and we discussed this during the IRC meeting. I guess we almost have this ready as a replacement now. I've been lagging in the last weeks with summarizing what happened during the meetings, so fortunately this week wasn't so bad. ;) 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. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day and 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 and will be travelling 21st December. I've started work on my improvements to zope.bugtracker. However, it looks like it's trickier than I imagined: we want to get a list of the most recent checkins on a project and, thus, need the repository URL. Unfortunately, unless I'm missing something, this isn't available from launchpad so all we have are naming conventions. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day: Tuesday 2010-11-30
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 #z...@freenode. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day and developer meeting today at 15:00 UTC
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 summarize as I was the only attendee of the meeting. So, just in case: if you're not happy with the topics I propose, please feel free to suggest others or just walk in. I'm happy to provide the regular space (and time) and am open to any issues regarding zope-dev. ... ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day and developer meeting today at 15:00 UTC
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 decisions well - we didn't find the grand solution, though. ;) Today, we'll meet, as always, in #z...@freenode at 15:00 UTC. This week my job of summarizing is suprisingly easy: nothing to summarize as I was the only attendee of the meeting. So, just in case: if you're not happy with the topics I propose, please feel free to suggest others or just walk in. I'm happy to provide the regular space (and time) and am open to any issues regarding zope-dev. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day and developer meeting today at 15:00 UTC
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, though. ;) Today, we'll meet, as always, in #z...@freenode at 15:00 UTC. Topics will be: - Follow-up on summit goals - The bicycle toolkit Christian ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day next tuesday, 2010-10-26
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 couple of CMF issues that I can look at including the current break to CMF + Zope 2.12 Otherwise I'll try and look at extending the bugtracking script as agreed with Theuni several months back. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day next tuesday, 2010-10-26
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 able to contribute something if you don't try to fit the whole day into your probably busy schedule. We'll hang out, as always, on IRC at #z...@freenode. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
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 Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
-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 never made it, busy with other stuff all day :-( jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkylobkACgkQRAx5nvEhZLKuCQCdH/n2vb9Wh58nFhZoEp3ARECB 268An0pOOifWDxJbIBZgnwnluTFRdjD1 =oiQC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 applauded them), but didn't realize it was a bug day. D'oh. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day reports
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: https://blueprints.launchpad.net/zope.app.generations/+spec/zope.generations - wrote a ticket and added a solution for review: https://bugs.launchpad.net/zope.copypastemove/+bug/620353 https://bugs.launchpad.net/zope.copypastemove/+bug/620353/comments/1 - rejected a ticket: https://bugs.launchpad.net/zope.catalog/+bug/189783 - released some packages, which contain the permission renaming from zope.app.dublincore.* to zope.dublincore.* zope.dublincore zope.app.file zope.app.container - updated migration documentation in ZTK accordingly: http://docs.zope.org/zopetoolkit/releases/overview-1.0a3.html#zope-dublincore-permission-renaming Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day reports
-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 https://bugs.launchpad.net/products.zsqlmethods/+bug/142501 https://bugs.launchpad.net/zope2/+bug/193122 Moved = https://bugs.launchpad.net/products.zsqlmethods/+bug/210398 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkx0y68ACgkQRAx5nvEhZLIhHACglzETKAdzldsyPK599zEnr1PK ZBUAoKNq1G+M2fCp4u3lnxKtquoNmNQZ =fQdS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day reports
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 (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-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 - https://bugs.launchpad.net/zope2/+bug/143533 - https://bugs.launchpad.net/zope2/+bug/143755 Fixed already = - https://bugs.launchpad.net/zope2/+bug/143765 Confirmed = - https://bugs.launchpad.net/zope2/+bug/143516 Invalid === - https://bugs.launchpad.net/zope2/+bug/143663 Incomplete == - https://bugs.launchpad.net/zope2/+bug/143509 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkw99MQACgkQRAx5nvEhZLI+iQCbBioRd/h25B+uiu5x7leZUz9n w7YAoJVHRQt7+mXd3xwEcR/QVmXwAeJj =qpzr -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-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 them under Python 2.7. Unfortunately I wasn't able to summon enough doctest-fu to make my stab work. Maybe somebody who doesn't break out in hives at the thought of running pdb inside a doctest can finish from the patch I attached to the issue. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw9+dsACgkQ+gerLs4ltQ4JYwCgq+d250vrheDX+dC8IwQ8NdTv QQUAn3uGP5STpliz5m0ErdygYMIcUpuP =cOpJ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 the buildout/test with the wrong python version. I usually prefer to let someone more experienced review my code, although it seems to be not worth it for this little fix. So to clarify - can I commit the patch to zope.testrunner after I verified that the tests are working fine on my local sandbox? You should be able to check in just fine -- do you mean zope.testing, or zope.testrunner? I checked in my changes to zope.testrunner already. I committed today - and yes, meant zope.testing :) Cheers -- Roman Joost www: http://www.romanofski.de email: ro...@bromeco.com signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
-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 wanted to release 'zope.testrunner', but wanted to check with you first. The patch is here: http://svn.zope.org/zope.testrunner/trunk/src/zope/testrunner/find.py?rev=113540view=diffr1=113540r2=113539p1=zope.testrunner/trunk/src/zope/testrunner/find.pyp2=/zope.testrunner/trunk/src/zope/testrunner/find.py I'm fine with letting you land it in zope.testing, or even tweak it on the zope.testruner side, if you see a better fix. 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. I usually prefer to let someone more experienced review my code, although it seems to be not worth it for this little fix. So to clarify - can I commit the patch to zope.testrunner after I verified that the tests are working fine on my local sandbox? You should be able to check in just fine -- do you mean zope.testing, or zope.testrunner? I checked in my changes to zope.testrunner already. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwbi6MACgkQ+gerLs4ltQ5mQACg0BejhsCAi8jw696URNPJ/KKh /6cAn0eFmusq+6EIlvSeudv+TdvpcG33 =6IHS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-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, https://bugs.launchpad.net/bugs/221151 and to release a 4.0.0b3 containing another three fixes: - - zope.testrunner's buildout makes failing tests https://bugs.launchpad.net/bugs/580083 - - Layer tearDown isn't called when running more processes, https://bugs.launchpad.net/bugs/579019 - - Remove requirement for the $Id$ marker in module docstrings, https://bugs.launchpad.net/bugs/569541 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwY4W0ACgkQ+gerLs4ltQ4YmwCgj5vEQwziTne3OpJLytEmF/CJ ufoAoJ+C+EIAO4gDdVSCq6DjoFOEx2P2 =7N8X -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-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 https://bugs.launchpad.net/zope2/+bug/143403 https://bugs.launchpad.net/zope2/+bug/143619 https://bugs.launchpad.net/zope2/+bug/143639 Marked Confirmed https://bugs.launchpad.net/zope2/+bug/143485 https://bugs.launchpad.net/zope2/+bug/143244 https://bugs.launchpad.net/zope2/+bug/143281 Marked Incomplete = https://bugs.launchpad.net/zope2/+bug/143621 https://bugs.launchpad.net/zope2/+bug/143704 Marked Duplicate https://bugs.launchpad.net/zope2/+bug/143743 Already fixed (marked Fix Released) === https://bugs.launchpad.net/zope2/+bug/143875 https://bugs.launchpad.net/zope2/+bug/142717 https://bugs.launchpad.net/zope2/+bug/143271 Moved to a different project https://bugs.launchpad.net/zope.pagetemplate/+bug/143923 https://bugs.launchpad.net/zope.formlib/+bug/143930 Marked Invalid == https://bugs.launchpad.net/zope2/+bug/143213 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwZDAMACgkQRAx5nvEhZLJCiACdEjleEjHTSQ+X4NbL3A0uRYXN x4kAn01PzhDHRjqhd07ki+jD0reJyWOA =Rq9Y -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day tomorrow: you're invited!
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 around during working hours in CEST) and others are happy to assist if you don't know how bug days work. For everyone who is used to bug days I'm also inviting you to write a short summary when you finish your bug day so that everyone can see where we're making progress. Happy bug daying everyone! Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] bug day?
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 - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] bug day?
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 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day status report
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 status, but I don't know who worked on this bug. Is it really fixed? Anybody? -- Paul Winkler http://www.slinkp.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day status report
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 http://collector.zope.org/Zope/1265 is still 'Pending' according to the collector. I can change the status, but I don't know who worked on this bug. Is it really fixed? Anybody? ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day status report
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 summarising this, I'd already joined the ranks driven to alcohol by tackling Zope bugs on a Friday afternoon ;-) Look forward to seeing you all again on the last Friday of June :-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day status report
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 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day status report (fwd)
[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 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 The #zope-dev channel is quiet now, but feel free to hop in and rev it up again :-) -- Paul Winkler http://www.slinkp.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 across to them too? ;-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 a bit of time) you will start thinking whether the next bug report is worth the effort. I do not think this is what the community should wish for... 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. How many other have we lost and are still suffering from as a result?! Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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, so they usually do get closed -- but it's more graceful when the OP does add more info. I intend to do this as well in the future. I assumed that bug reports posted years ago with no followup had little or no chance of ever being clarified now. 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. -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 bug-fixers. No it doesn't. Closing bugs that can't or won't be fixed is just sweeping crap under the carpet. I think the current collector is a bit flawed in the available statuses. I totally agree ;-) There is no specific way to denote an issue as won't fix which means that it is possibly a bug, but either it is not fixable, is not deemed worth fixing, cannot be fixed with the information provided, or nobobdy has fixed it for years so it's not gonna happen. Yep, I think a Won't fix status would be a good thing (tm). I'd even offer to help but I see the other chris has already run into a brick wall o nthat front :-( I chose to reject the bug hoping that it would cause a reaction, which it did. I'll admit that reject is not exactly the right status, however the right status is not currently an option for the collector. Yep, although I think Dieter's comment (and this follow-up by me certainly is) was commenting on the wider issue of people rejecting or closing bugs with too much haste or without addressing the issue in a satisfactory way (such as maybe adding to a mythical known bugs that currently won't be fixed file is /doc. I know Andreas is certainly pretty bad on this. It's helpful to weed out the crap (ie rubbish postings, or stuff that should be on the list, or stuff that's in the wrong tracker) but just rejecting quickly without giving good explanation, documenting elsewhere or filing an issue in the right tracker feels pretty bad from my point of view :-S cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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 rejecting or closing bugs. It feels inconsistent right now, and the above kind of attitude, which keeping the number of open issues in the tracker to a minimum, isn't really helping to produce a better quality piece of software. ...and that is our aim here, right? If the bug report is understandable, and repetable and indeed a bug, and not a misunderstanding, and the community thinks it should be fixed, then yes. But there are many instances where bugs should be closed without anything being changed at all. Closed is wrong here, we need a won't fix state... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
--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 mostly with Lennart. Anonymous bug reports is one thing. Discussing or solving bugs for ghosts is another one. I tend to oversee anonymous bug reports. If people have something to say or to report they should at least leave their email address. Same with support question..they are completely off-topic. We provide support through the lists, not through the collector. Another point: incomplete but reports. ..if people file issues with incomplete data and if they are not willing to provide additional data I reject such issueshard and brutal. -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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,#511,#532,#540,#543, #544,#545,#546,#553,#562,#574,#584,#602,#637,#644,#654,#658,#666, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300. However, you closed (at least one) bug reports without resolving the the issue. Make no mistake about this. Had I not spend yesterday on a plane, there would have been many issues closed without resolving it. 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. :) You should not close true bug reports. Doing so is (in my view) a bad approach to quality. I do not think this is good practice... Bug reports should remain open until they are either fixed or can no longer occur. If the bug report is understandable, and repetable and indeed a bug, and not a misunderstanding, and the community thinks it should be fixed, then yes. But there are many instances where bugs should be closed without anything being changed at all. In my view this should only happen for reports that are not bugs. Reports (of some quality) about true bugs (or unanticipated behaviour) are valuable even when nobody plans to actually fix them. They should not be closed just because you do not plan to fix them in the near future... 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 a bit of time) you will start thinking whether the next bug report is worth the effort. I do not think this is what the community should wish for... -- Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300. However, you closed (at least one) bug reports without resolving the the issue. I do not think this is good practice... Bug reports should remain open until they are either fixed or can no longer occur. They should not be closed just because you do not plan to fix them in the near future... -- Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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,#495,#511,#532,#540,#543, #544,#545,#546,#553,#562,#574,#584,#602,#637,#644,#654,#658,#666, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300. However, you closed (at least one) bug reports without resolving the the issue. I do not think this is good practice... Bug reports should remain open until they are either fixed or can no longer occur. They should not be closed just because you do not plan to fix them in the near future... If a bug will not be fixed, judged by:: - The bug description - The time it has remain open without action - The lack of a patch provided for the bug - The lack of assignment or interest of a sponsor This means it is an unsponsored bug. It should not remain open forever. 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 bug-fixers. I think the current collector is a bit flawed in the available statuses. There is no specific way to denote an issue as won't fix which means that it is possibly a bug, but either it is not fixable, is not deemed worth fixing, cannot be fixed with the information provided, or nobobdy has fixed it for years so it's not gonna happen. I chose to reject the bug hoping that it would cause a reaction, which it did. I'll admit that reject is not exactly the right status, however the right status is not currently an option for the collector. Since I can see you feel strongly about this issue, please feel welcome to reopen to bug or change it to a status that better suits it. At this point I see no chance of it being fixed without a champion, however. -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
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,#644,#654,#658,#666, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300. However, you closed (at least one) bug reports without resolving the the issue. Make no mistake about this. Had I not spend yesterday on a plane, there would have been many issues closed without resolving it. 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 do not think this is good practice... Bug reports should remain open until they are either fixed or can no longer occur. If the bug report is understandable, and repetable and indeed a bug, and not a misunderstanding, and the community thinks it should be fixed, then yes. But there are many instances where bugs should be closed without anything being changed at all. They should not be closed just because you do not plan to fix them in the near future... True. But if they are not planned to be fixed at all, then they should be closed. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day!
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! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
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, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300. Thanks to all who participated! -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day?
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 next week. Thoughts? Brian Lloyd[EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day?
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 releases by the end of next week. Thoughts? Fine by me. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day?
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 you weren't saying squat kid. -Buddy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day Followup
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 into the HEAD, otherwise they are likely to reappear in 2.7. Again thanks to everyone for a great bug day! -Casey ___ 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 http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] bug day
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 http://collector.zope.org/Zope. Anyone may participate. It is best if you can set aside an entire day for bug-squashing, but any amount of time you can spare is obviously useful. 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. Thanks! - C ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] bug day
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 days has been *concensus* about which bugs can be forgotten about, or rejected, and which are most important. You dont need to be a hardened zope developer to make a valuable contribution. ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] bug day
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 last two bugs days has been *concensus* about which bugs can be forgotten about, or rejected, and which are most important. You dont need to be a hardened zope developer to make a valuable contribution. What a coincidence. A few days ago I wrote some text regarding 623 issue (but not posted) which also mentions consensus issue: Consensus problem - Unicode support is particularly hard to have the consensus, as the benefit/impact of the specification is significantly different among people of different regions in the world. As Zope's popularity is becoming worldwide, difference of the impacts of cultural-sensitive specification is becoming larger. For instance, while one region may get benefit from one change in specification without problem, other region may suffer from it. Also, it's harder to realize/measure the impacts on different regions, as it requires deep knowledge of different cultures. The difficulty of I18N lies rather in that aspect, not in technical difficulties. Regards, --- Heiichiro NAKAMURA [EMAIL PROTECTED] ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-Coders] Re: [Zope-dev] Bug Day 8/02 recap
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 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 with them right now. Still, it's nice to see activity at the very least :-) cheers, Chris ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-Coders] Re: [Zope-dev] Bug Day 8/02 recap
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 with them right now. Yes, there were a lot of rejections. Out of the ones I myself made, most were due to the bug report being invalid -- that happens a *lot* with any issue reporting system. Several also had to be dumped because more info was asked for six months ago and never received. We discussed most of them on IRC, which was truly the real benefit of having a Bug Day: getting that rough consensus needed to take action. I also made several resolutions, most of which were bugs that were fixed before, advertently or inadvertently. Very little code was checked in; most resolutions seemed to be bugs that had already disappeared for one reason or another. I consider this a good thing. :-) -- Matt Behrens [EMAIL PROTECTED] URL:http://zigg.com/ msg5/pgp0.pgp Description: PGP signature
Re: [Zope-dev] Bug Day 8/02 recap
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 Collector activities! Dieter ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day 8/02 recap
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 note that I am *very* pleased with recent Collector activities! Dieter 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! :) Good work guys! Adrian... -- Adrian Hungate EMail: [EMAIL PROTECTED] Web: http://www.haqa.co.uk ___ 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 http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day 8/02 recap
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 think it would be good to hold another one in September; how's the 11th at 9 AM US/Eastern? (For the curious, we squashed #101, #115, #121, #46, #129, #27, #297, #29, #148, #461, #497, #38, #501, #106, #453, #69, #37, #40, #74, #95, #82, #507, #53, #168, #408, #81, #83, #90, #93, #104, #113, #61, #117, #127, #132, #134, #152, #268, #192, #13, #92, #179, #177, #518, AND #332.) -- Matt Behrens [EMAIL PROTECTED] ___ 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 http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day Wednesday 8/14.
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 bug-squashing activities is welcome to join in. Don't worry if you're not on the Zope commit-privileges list, There will be at least a few people online with commit privileges that can help you commit your favorite bugfix. It's tenatively scheduled for Wed. 8/14, 9am EST (I think that's 2pm GMT). If you're interested in participating, please join the #zope-coders channel on irc.openprojects.net at that time. Thanks! - C ___ 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 http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day June 2002 results
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, plus chrism@ worked tirelessly on the Transience problems. Total bugs resolved, then, is 10. Next Bug Day, provided folks are keen on it, would then be Thursday, July 18 (IIRC, the Europeans preferred Thursdays), starting at 9 AM US/Eastern. ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day for June?
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 thing for all of us Europeans I guess. How about _next_ Thursday (the 20th)? Things are pretty hectic here this week, and I'd like to try to push out 2.6 a1 (which we're already running a little behind on). -Brian Hi all - I never heard anything back from this. Are we still on for tomorrow? Hmm, too much rush here, sorry, I won't make it. Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ 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 http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug Day for June?
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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day for June?
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 -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ 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 http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug Day for June?
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. ___ 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 http://lists.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Bug Day for June?
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 _next_ Thursday (the 20th)? Things are pretty hectic here this week, and I'd like to try to push out 2.6 a1 (which we're already running a little behind on). Brian Lloyd[EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com ___ 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 http://lists.zope.org/mailman/listinfo/zope )
