On Wed, Mar 19, 2025, at 02:46, Bron Gondwana wrote: > A bunch of us are sitting at IETF122 in Bangkok, working our way through old > issues and closing them out, giving them better labels, or... if they're > really tiny, just doing them. > […] > Our intention isn't to forget real bugs, but just to bring the issue list > down to a manageable size - if something has had no action for years and > nobody is noticing it, there's no point keeping it there and making the issue > count look un-approachable! But - if we close something in error, please do > feel free to re-open it or create a new issue.
I think this went really well. We closed well over half the issues. That said, being in a position where closing half the issues in a weekend is possible isn't great, and we'd like to avoid it coming up again. Here are some things we've more or less decided on: • issues are work work we plan on doing, not a collection of maybe-someday ideas • new issues should be triaged promptly • triage will generally do one of the following (I know, more than three): • agree that the issue is work that should get done (which will probably creating a matching issue in Fastmail's internal work tracker) • agree that the issue describes a defect, but declare we don't plan to work on it soon, in which case we'll move a note on it into the source code as an "XXX" comment in the right place • reply "this does not warrant the time to add a code comment to it, but a patch might be applied if provided" • disagree that the issue represents a real problem • *maybe *leave some issues in a "real problem, not being worked on soon" state, for features that Fastmail does not really use or support (canonical example: murder) • we will probably add a has-been-triaged label to help So, expect to see *even more* processing through of these issues. Nobody is happy about having a big pile of issues that seemed like maybe they were in line to get done, but are now being marked "no plans to do this", but we think that this is the practical way to get things into a more sustainable, understandable state. -- rjbs ------------------------------------------ Cyrus: Devel Permalink: https://cyrus.topicbox.com/groups/devel/T831869076780043c-Mc9613a93fc79bd183443c85a Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
