Request for discussion: lowering the backlog of old Trac tickets.

Chris Jones jonesc at hep.phy.cam.ac.uk
Mon Apr 30 19:09:33 UTC 2018


> Anyway, that was what I wrote. I'd be interested in hearing other
> people's thoughts.

In short, I would agree with you. MPs current trac is bogged down with too many open tickets such that it is arguably not 100% fit for purpose. I certainly have preferred to largely ignore it as much as I can, since the move to git.

So yes, I would agree open tickets that show no sign of progress, have had no comments in a long time (say >1 year) and relate to something not seen widely (I would suggest those last two criteria amount to the same...) then closing the port along the lines of

"Closing due to lack of activity. Please open a new ticket if still an issue with up to date versions"

is perfectly reasonably way of getting the list down. I in fact did this to a few assigned to myself today.

I would also argue we are using the same system, for two different things. Short term bug reports and longer term 'work goals' are not the same, but we seem to mix them up in the same system. Maybe some way (label ?) to identify tickets that are going to be longer term is required ?

Chris



More information about the macports-dev mailing list