[Gluster-devel] Backlog/Improvements tracking
skoduri at redhat.com
Tue Apr 30 10:45:17 UTC 2019
To track any new feature or improvements we are currently using github .
I assume those issues refer to the ones which are actively being worked
upon. How do we track backlogs which may not get addressed (at least in
the near future)?
For eg., I am planning to close couple of RFE BZs .. which were
filed to improve upcall mechanism, as there is no active development
happening in those aspects. But at the same time I like to retain the
list for future reference (in case any new member like to take up).
Can we use github itself to track all the feature-gaps of a component in
one issue (note: it may be in open state forever) or is it better to
document these as limitations in the admin/developer guide & close BZ/issue?
More information about the Gluster-devel