[influxdb] Re: exploring ways to keep GitHub Issues manageable

[[e-mail]]

Hello to the InfluxData community!
The number of open issues in the InfluxDB repo is growing, and we at InfluxData would like to find a way to maintain a steady-state number open issues. Over 25% of our open issues are feature requests. Some of them are excellent ideas but not likely to be implemented for some time, if ever. It seems wasteful to keep hundreds of issues open for a year or more, but at the same time it's not productive to have new users opening the same issues over and over when they don't find one already in the repo.
We'd like your feedback about a possible approach. Please remember this is a proposal, not a definite change. Our goals are to 
Shrink the number of open issues to make issue triage and searching easierKeep open issues focused on currently actionable itemsPreserve context for future development
https://github.com/influxdata/influxdb/issues/5930 collects all the feature requests for new InfluxQL functions and operators into one place. When we're ready for work on Functions the developers can use this master issue to see what is out there, investigate the individual issues, and take action. When work starts on a new function the conversation can happen in a reopened issue, a new issue, or in the PR.
What do you think in general of the collection of issues idea?
What about the format of the proposed feature collection issue?
The next question is more controversial. We would like to close the original issues referenced in the feature collection issue. The comments won't be lost, and the conversation can continue on individual issues, but long-standing and not immediately-actionable issues won't be polluting searches. (Note that users searching for individual functions would still find an open issue referencing HISTOGRAM.)
How do you feel about closing feature requests that are good ideas but not short-term goals?
Do you think this would be too confusing for users new to InfluxDB?Have you seen any other approach that accomplishes the same goals?--
Sean Beckett
Director of Support and Professional Services
InfluxDB

Dear Sean:

Do you have a release date for the LAG and HISTROGRAM functions?
Or it was suspend?

Thanks.