[Gluster-devel] Marking bugs as a Feature Request, and listing all requested features

[Niels de Vos]

On Tue, Oct 21, 2014 at 01:39:18PM +0200, Niels de Vos wrote:
> Hi all,
> 
> during last weeks Bug Triage meeting, we discussed a little about
> marking bugs as Feature Request or Requested Feature Enhancement (RFE).
> In the Buzilla instance that we use, at least two different markers are
> used:
> 
> a. [FEAT] 'tag' in the subject of the bug
> b. 'FutureFeature' as a keyword in the bug
> 
> We should pick one for our workflow, and stick to that. Does anyone have
> an opinion about this? Our current inclination is to go with the keyword
> approach because it makes searching and reporting a little easier.

We have settled on marking Feature Requests with the "FutureFeature"
keyword. Bugs that have an RFE or FEAT tag in the subject now also have
the keyword added.

The Bug Triage guidelines have been amended to include the
"FutureFeature" keyword, thanks Humble!
- http://www.gluster.org/community/documentation/index.php/Bug_triage#Keywords

The following Bugzilla query shows all the open feature requests:
- https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&keywords=FutureFeature&keywords_type=allwords&product=GlusterFS

Or, use the bugzilla commandline (from the python-bugzilla package):
  $ bugzilla query \
        --product=GlusterFS --bug_status=OPEN --keywords=FutureFeature

Some of these features may already have been implemented in current
versions. If that is the case, feel free to mark the bug as a duplicate
from the one that contains a link to the patch and/or version that
contains the feature.

If someone finds additional bugs that are a feature request, please add
FutureFeature in the keyword box in the bug.

Thanks,
Niels