This is an attempt at getting some feedback on requirements for our
various bug/feature tracking needs. I have deliberately omitted the
'options' section, so we can focus as a group on requirements only at
this point.
At the moment, we have or need a way to track both types of issues
from the following standpoints:
* Upstream project
* Fedora releases
* RHEL/product releases
This is the list I have so far, with some feedback from others, though
not as much as I would like.
== upstream tracker ==
* report code level stuff here. This really needs to track what is
in github/master at any given point in time.
*relate this upstream bug to something released -either fedora
or rhel (relation could be established by this system or the
other system as long as it works)
* ability to define features that are comprised of many tasks
* set some kind of due date to allow mapping to sprints
== Fedora ==
* Choose a place where someone can report a bug against a fedora
rpm, instead of always reporting it against the product
* report fedora bugs here (or clone them from product) --
needs to track what is in the fedora rpms
* We already have existing BZ components, listed here:
**
https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=aeol...
**
https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=aeol...
**
https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=aeol...
**
https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=ruby...
**
https://bugzilla.redhat.com/buglist.cgi?product=Fedora&component=ruby...
== CloudFormsCloudEngine (details out of scope here) ==
* report product bugs here (tracks what is in the product RPMs)
-j