[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 )
[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 )
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 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 )
