Willy, Am 12.01.21 um 11:49 schrieb Willy Tarreau: >> Maybe it makes sense to look through the list of currently open feature >> requests and close the ones that are very unlikely to be implemented (or >> unlikely to be implemented in the next few years) to clean up the >> tracker a bit. > > Probably that we should indeed do something like that. But once closed > they're harder to find, so maybe we could proceed by adding a page in > the wiki with a few links: > - opened feature requests (not handled yet) > - opened feature requests (in progress) > - closed feature requests (implemented) > - closed feature requests (not implemented or differently) > > And we'd simply tag "fixed" the ones implemented as desired. For the
In fact I already did that for all the features I was able to keep track of. See: https://github.com/haproxy/haproxy/issues?q=is%3Aissue+label%3A%22type%3A+feature%22+is%3Aclosed > not-yet vs wip I don't see any currently valid label, which also makes > me think that we could *possibly* benefit from an "in progress" which > is valid both for bugs and features. However one could argue that an > issue without a status label would imply it's in progress, which would > then suggest that we'd need to add a "status: triage" to new features > just like new bugs. I'm not sure that's necessary. For features there IMO only three states: - Implemented: Closed + Fixed. - Not Planned: Closed + No Label. - Maybe Planned: Open. Best regards Tim Düsterhus
