I'm not sure the benefit of marking these tickets obsolete is. You may as well just close them. Someone can reopen them if they disagree. There could be some arguent for adding tests from these old tickets but tbh they are so old that if the bug still exists there is probably a newer ticket. On Sat, May 4, 2019 at 10:31 PM Kevin Buhr wrote:

Okay, I've added a new "obsolete" label: "Old issues that no longer apply and are in a short waiting period before closing." I'll start going through the low-hanging fruit adding comments and sticking this label on them, with the idea of going back and closing them after, say, 4 weeks with no complaints. After I've gone through a few of these and gained some experience with it, I'll try to draft some guidelines for handling old tickets.

Anyway, please let me know if this process starts to get irritating.

-- Kevin Buhr

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

They can be closed outright, but marking them with obsolescence is still useful for future reference, and is negligible. ________________________________ From: ghc-devs on behalf of Matthew Pickering Sent: Saturday, May 4, 2019 10:56:49 PM To: Kevin Buhr Cc: GHC developers Subject: Re: Is cleaning up old issues worthwhile? I'm not sure the benefit of marking these tickets obsolete is. You may as well just close them. Someone can reopen them if they disagree. There could be some arguent for adding tests from these old tickets but tbh they are so old that if the bug still exists there is probably a newer ticket. On Sat, May 4, 2019 at 10:31 PM Kevin Buhr wrote:

Okay, I've added a new "obsolete" label: "Old issues that no longer apply and are in a short waiting period before closing." I'll start going through the low-hanging fruit adding comments and sticking this label on them, with the idea of going back and closing them after, say, 4 weeks with no complaints. After I've gone through a few of these and gained some experience with it, I'll try to draft some guidelines for handling old tickets.

Anyway, please let me know if this process starts to get irritating.

-- Kevin Buhr

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

| I just want to second comments others have said about the value of this | kind of activity. It is most certainly *not* annoying! Indeed. Thank you for doing this. Wherever possible, please consider adding a regression test. That makes sure the bug *stays* fixed. Simon | -----Original Message----- | From: ghc-devs On Behalf Of Richard | Eisenberg | Sent: 06 May 2019 04:05 | To: Kevin Buhr | Cc: ghc-devs@haskell.org | Subject: Re: Is cleaning up old issues worthwhile? | | I just want to second comments others have said about the value of this | kind of activity. It is most certainly *not* annoying! If you're right and | there is a migration issue, then it is indeed reasonable to stop and get | feedback, but I'm (for one) comfortable having you close tickets that you | cannot reproduce in a modern GHC -- as long as you're careful about | checking this. (For example, perhaps an old ticket has some code that | doesn't make sense with Applicative being a superclass of Monad. Before | labeling the issue as unreproducible, it would be wise to update the | example first.) The worst case scenario is that someone reopens. | | Many thanks for this work! | Richard | | > On May 4, 2019, at 6:49 PM, Kevin Buhr wrote: | > | > Well, after going through a few of these, I realize that there's some | relevant Trac metadata (specifically, "Resolution" fields of | "ResolvedWorksForMe", "ResolvedFixed", etc.) for all of the ones I've | found. It looks like certain old bugs that were somehow "resolved" but | not "closed" in the old system came over as open tickets in GitLab. This | is maybe related to gitlab-migration issue #43. So, I'll stop now. | > | > -- | > Kevin Buhr | > | > _______________________________________________ | > ghc-devs mailing list | > ghc-devs@haskell.org | > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs | | _______________________________________________ | ghc-devs mailing list | ghc-devs@haskell.org | http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs