periodic auto actions on bug tracker
I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed. cheers -ben
Itâs a great idea - I too have a good look at what I previously reported and decide if itâs still relevant and whether it makes sense to still pursue it. Sent from my iPhone
On 9 Dec 2018, at 06:20, Ben Coman <btc@openinworld.com> wrote:
I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance.
It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed.
cheers -ben
On 9 Dec 2018, at 01:50, Ben Coman <btc@openinworld.com> wrote:
I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance.
It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed.
Yes, that is a good idea. I will add it to the things to do for the issue tracker / integration related scripts. Marcus
Marcus Denker-4 wrote
I support the auto-closing of old tickets to avoid bug bankruptcy ... Yes, that is a good idea.
I thought we already did that. Don't we even have a stale/timeout tag to distinguish from other reasons for closing and help find them again later if needed? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
On 13 Dec 2018, at 03:35, Sean P. DeNigris <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
I support the auto-closing of old tickets to avoid bug bankruptcy ... Yes, that is a good idea.
I thought we already did that. Don't we even have a stale/timeout tag to distinguish from other reasons for closing and help find them again later if needed?
We close them with a timeout tag. But we do not send a public mail âhey, these tickets will be closed next weekâ. Only the *owner* gets a message on closing. Marcus
participants (4)
-
Ben Coman -
Marcus Denker -
Sean P. DeNigris -
Tim Mackinnon