Re: Current Issues with Patch Review Workflow Using git.guix-patches.cbaines.net

[jgart]

> I don't think automatically closing older issues is helpful, they still
> need looking at.

Or instead of closing them, put the patch into a state that is not open. Like 
an archived state or some other state that does not require action until 
someone takes ownership of the issue and resolves it.

I think this can prevent being overwhelmed by the number of open issues that 
are not high priority, lack reviewers, or are so grossly outdated and that they 
require completely starting from scratch in order to work on it.