Number of open issues is less than 100

[brianhuffman]

For much of Cryptol's history we've had at least a hundred open tickets on the github issue tracker. Lately we've dipped below 100, which probably means that we're getting a little behind on filing new ones.

We should close this ticket once the number is back up where it should be; of course it might be necessary to open the ticket again if the numbers dip again in the future.

[TomMD]

We still need three more issues at time or writing. I can revert the oldest 3 bug fixes that revert cleanly and re-open those tickets. Thoughts?

[yav]

Hm, I am sensing a problem here. Say we introduced 3 more issues. Then we would be at a 100 issues, which means that we could close this ticket, but then we'd have to open it straight away...

[elliottt]

Clearly someone will need to take on the full time opening/closing responsibility. Nominations for the position?

[weaversa]

Currently in QuasiSpace here.

[brianhuffman]

We're currently at 101, so I'm closing this ticket for now.

[yav]

Uhm, things seem to be getting worse.

[brianhuffman]

It seems like we're doing a pretty good job of filing new tickets lately: In the past month (June 24 to July 24) we have seen one pull request and 22 new tickets filed (#517 to #539), up from only 8 the previous month. But apparently we need to work even harder!

[weaversa]

79 is pretty good!

[brianhuffman]

With #599, we now have more than 100 issues again.

[robdockins]

🤷

[brianhuffman]

I just opened 4 new tickets! See #616, #617, #618, and #619. This brings us back up over 100.

[brianhuffman]

Once again we're comfortably over the 100 mark.

[weaversa]

Just dipped under.

[WeeknightMVP]

This issue can be closed again for now. Perhaps you could use the GitHub API to dynamically update the issue status? Sounds like a great use of bandwidth! (For this, the guide suggests a webhook, as aggressive polling is frowned upon.)