Agreed.
stef
On Sep 28, 2013, at 5:39 AM, Sean P. DeNigris s...@clipperadams.com wrote:
we have a couple of statuses that come close to that:
Resolved Postponed
indeed Postponed should be close to stale and I understand Sean concerns.
Yes, that sounds like it could work. If we
Hello,
The issue tracker is again at over 500 entries:
https://pharo.fogbugz.com/f/filters/33/All-by-project
Please, if you submitted a bug in the past, check it's status!
- Maybe someone asked you a trivial question that *you* can answer
in 10 seconds, but if you don't, the issue can
Thank you for taking care of this, Marcus!
While we're on the subject, there have been some issues which were not
resolved that were closed due to e.g. inactivity. I totally understand the
need to keep the bug tracker to a manageable size, but I feel that something
is lost when we do this. For
On Sep 26, 2013, at 2:34 PM, Sean P. DeNigris s...@clipperadams.com wrote:
Thank you for taking care of this, Marcus!
While we're on the subject, there have been some issues which were not
resolved that were closed due to e.g. inactivity. I totally understand the
need to keep the bug
Marcus Denker-4 wrote
The problem is that if we have over 500 entries, people just give up.
They say what use is it to fix 1, there are just too many.
Okay, so I think a Resolved status like Stale would be a good
compromise. Then we can close the issue, but it will be tagged as to the
reason,
On Sep 26, 2013, at 3:57 PM, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-09-26, at 10:23, Sean P. DeNigris s...@clipperadams.com wrote:
Marcus Denker-4 wrote
The problem is that if we have over 500 entries, people just give up.
They say what use is it to fix 1, there are just too
I agree, closing bugs , or deleting them, on the grounds that none has
comment on them for a very long time is a very bad idea. Pharo has a small
crowd of users and I seriously doubt they care much of the bug report
process. That does not make a bug any less important though.
In the end of the
