<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:"Yu Gothic"}
@font-face
{font-family:Calibri}
@font-face
{}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
.x_MsoChpDefault
{}
@page WordSection1
{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-GB" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">They can be closed outright, but marking them with obsolescence is still useful for future reference, and is negligible.</p>
<p class="x_MsoNormal"> </p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> ghc-devs <ghc-devs-bounces@haskell.org> on behalf of Matthew Pickering <matthewtpickering@gmail.com><br>
<b>Sent:</b> Saturday, May 4, 2019 10:56:49 PM<br>
<b>To:</b> Kevin Buhr<br>
<b>Cc:</b> GHC developers<br>
<b>Subject:</b> Re: Is cleaning up old issues worthwhile?</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">I'm not sure the benefit of marking these tickets obsolete is. You may<br>
as well just close them. Someone can reopen them if they disagree.<br>
<br>
There could be some arguent for adding tests from these old tickets<br>
but tbh they are so old that if the bug still exists there is probably<br>
a newer ticket.<br>
<br>
On Sat, May 4, 2019 at 10:31 PM Kevin Buhr <buhr@asaurus.net> wrote:<br>
><br>
> Okay, I've added a new "obsolete" label: "Old issues that no longer<br>
> apply and are in a short waiting period before closing." I'll start<br>
> going through the low-hanging fruit adding comments and sticking this<br>
> label on them, with the idea of going back and closing them after, say,<br>
> 4 weeks with no complaints. After I've gone through a few of these and<br>
> gained some experience with it, I'll try to draft some guidelines for<br>
> handling old tickets.<br>
><br>
> Anyway, please let me know if this process starts to get irritating.<br>
><br>
> --<br>
> Kevin Buhr <buhr@asaurus.net><br>
><br>
> _______________________________________________<br>
> ghc-devs mailing list<br>
> ghc-devs@haskell.org<br>
> <a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
_______________________________________________<br>
ghc-devs mailing list<br>
ghc-devs@haskell.org<br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</div>
</span></font>
</body>
</html>