bug tracker gardening for bugday
Hello, I've added the tag "bugday20100424" to some bugs for the bugday. Feel free to do the same with others. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Action causes more trouble than thought
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam GROSZER wrote:
Hello,
I've added the tag "bugday20100424" to some bugs for the bugday. Feel free to do the same with others.
Here is the Launchpad tag page for it: https://bugs.launchpad.net/zopetoolkit/+bugs?field.tag=bugday20100424 I have updated the bugday wiki page with that link. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvPLK4ACgkQ+gerLs4ltQ616ACgwrF4PEHRONk/0yhISlmcp7pr FucAn3+ntgHl+SgzB7pct41e63vB5pww =4OHH -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tres Seaver wrote:
Adam GROSZER wrote:
Hello,
I've added the tag "bugday20100424" to some bugs for the bugday. Feel free to do the same with others.
Here is the Launchpad tag page for it:
https://bugs.launchpad.net/zopetoolkit/+bugs?field.tag=bugday20100424
I have updated the bugday wiki page with that link.
I have also tagged a bunch of other bugs (mostly those with patches) with the tag -- it would be good to adopt a culture where bugs with patches (or branches) never languish. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvPMo4ACgkQ+gerLs4ltQ7tbACgqOra61UYu47doXyihlC/6+bh 9bcAn0OpptJDEIPHL2J4dL4Nnukjr31p =q+Vu -----END PGP SIGNATURE-----
On Wed, Apr 21, 2010 at 2:14 PM, Tres Seaver <tseaver@palladion.com> wrote:
I have also tagged a bunch of other bugs (mostly those with patches) with the tag -- it would be good to adopt a culture where bugs with patches (or branches) never languish.
"There's a view for that!": https://bugs.edge.launchpad.net/zopetoolkit/+patches -- Sidnei
Hello Tres, You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month. Anyone unhappy with that should speak up or reopen the bug. Wednesday, April 21, 2010, 7:14:54 PM, you wrote: TS> -----BEGIN PGP SIGNED MESSAGE----- TS> Hash: SHA1 TS> Tres Seaver wrote:
Adam GROSZER wrote:
Hello,
I've added the tag "bugday20100424" to some bugs for the bugday. Feel free to do the same with others.
Here is the Launchpad tag page for it:
https://bugs.launchpad.net/zopetoolkit/+bugs?field.tag=bugday20100424
I have updated the bugday wiki page with that link.
TS> I have also tagged a bunch of other bugs (mostly those with patches) TS> with the tag -- it would be good to adopt a culture where bugs with TS> patches (or branches) never languish. TS> Tres. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Many people today don't want honest answers insofar as honest means unpleasant or disturbing. They want a soft answer that turneth away anxiety. - Louis Kronenberger
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month. Anyone unhappy with that should speak up or reopen the bug.
+lots jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkvQBp4ACgkQRAx5nvEhZLI0rwCeNk1bRYU3KIyyVDulUThtu+Tq glsAoJvy1qIqMrHKwyRpTTPeHGDQSCIq =YplW -----END PGP SIGNATURE-----
Hello, JV> On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month. Anyone unhappy with that should speak up or reopen the bug.
JV> +lots JV> jens What should be the timeframe? 5 years? 3 years? 2 years? -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Life is short and we have never too much time for gladdening the hearts of those who are traveling the dark journey with us. Oh be swift to love, make haste to be kind. - Henri Frederick Amiel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/22/10 11:11 , Adam GROSZER wrote:
Hello,
JV> On 4/22/10 09:24 , Adam GROSZER wrote:
Hello Tres,
You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month. Anyone unhappy with that should speak up or reopen the bug.
JV> +lots
JV> jens
What should be the timeframe? 5 years? 3 years? 2 years?
I'd say 3 years. However, I have no experience how other projects handle this. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkvQFRwACgkQRAx5nvEhZLI9NACfbyMcUSaLfeqkABXM/m6vMyW9 W7sAnA8yVv11COfN8vbHikKDaPbL1wPY =Hyw9 -----END PGP SIGNATURE-----
On Thu, Apr 22, 2010 at 09:24, Adam GROSZER <agroszer@gmail.com> wrote:
Hello Tres,
You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month.
There is a state "not enough information" or something like that, and we can close bugs that has been in that state for a period of time. If the bug can be reproduced, it should not be closed just because it's old, even if it's 8 years old. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lennart Regebro wrote:
On Thu, Apr 22, 2010 at 09:24, Adam GROSZER <agroszer@gmail.com> wrote:
Hello Tres,
You think we have a chance to get rid of old cruft? Like 5 years old nothing happened since then bugs. I think we should add a tag "too old", add a note to warn subscribers, then set a status "Won't fix" after a month.
There is a state "not enough information" or something like that, and we can close bugs that has been in that state for a period of time. If the bug can be reproduced, it should not be closed just because it's old, even if it's 8 years old.
"Incomplete" is the auto-expiring state: if nobody responds in 30 days, it automatically disappears. I agree that we should at least attempt to reproduce even really old bugs before assigning them 'wontfix' status (if we can't) or 'incomplete' (if we need more information). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvQQvMACgkQ+gerLs4ltQ5akQCguLU/iVzTBp7FKb8u4zLcUyYY UiQAmgMOQKMasmg83GRG0JBdvZBtiu7H =z1bO -----END PGP SIGNATURE-----
On Thu, Apr 22, 2010 at 2:37 PM, Tres Seaver <tseaver@palladion.com> wrote:
"Incomplete" is the auto-expiring state: if nobody responds in 30 days, it automatically disappears.
I agree that we should at least attempt to reproduce even really old bugs before assigning them 'wontfix' status (if we can't) or 'incomplete' (if we need more information).
Speaking from my experience with cleaning up the Zope2 tracker: Zope is remarkably stable and there's some really old but still completely accurate tickets in the tracker. Just because anything is old, doesn't mean it's not valid anymore. I found some really good patches from 8 years back ;) I think you should use the "incomplete" status exactly when something is that: there's not enough information in the ticket to reproduce it. There's another category of tickets which describe problems with no longer maintained or outdated versions. Something along the lines of "Zope X3.0b1 is missing a Windows binary installer". Those I'd close with an immediate "won't fix". Hanno
participants (6)
-
Adam GROSZER -
Hanno Schlichting -
Jens Vagelpohl -
Lennart Regebro -
Sidnei da Silva -
Tres Seaver