[Gluster-devel] Backlog/Improvements tracking

Kaleb Keithley kkeithle at redhat.com
Tue Apr 30 11:06:35 UTC 2019

Yes, please open github issues for these RFEs and close the BZs.


On Tue, Apr 30, 2019 at 6:46 AM Soumya Koduri <skoduri at redhat.com> wrote:

> Hi,
> 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 [1]..[3] 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?
> Thanks,
> Soumya
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1214654
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1214644
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1200264
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20190430/f72550ed/attachment.html>

More information about the Gluster-devel mailing list