title: Managing the list of workarounds in a long-lived project
body: <p>We are creating a big project that will live and be improved for approximately 10 years.</p>
  
  <p>Already in our code base, there is a lot of code for specific browser incompatibilities, workarounds for different bugs in browsers, 3rd party tools and libraries and so on. The code itself usually works fine, but in time, it will become harder to debug, read and refactor.</p>
  
  <p>Is there some standard way to manage the issues and remove the code once it is not needed?</p>
  
  <p>Ideas that come to my mind:</p>
  
  <ol>
  <li>Manually maintain a table of workarounds with links to issues -> instructions how to remove them. Possibly with some metadata.</li>
  <li>Set up a task that will create low priority entry in the company issue tracking system if:
  
  <ul>
  <li>Status changes on the Github issue page.</li>
  <li>Browser usage drops below a threshold (to identify workarounds that are no longer necessary).</li>
  <li>Code coverage detects that the "if branch" is no longer visited.</li>
  <li>The issue was not revisited in a long time.</li>
  </ul></li>
  </ol>