Bugs and RFE's for Fedora Workstation
Paul W. Frields
stickster at gmail.com
Fri Dec 5 16:57:38 UTC 2014
On Fri, Dec 05, 2014 at 10:03:25AM -0500, Ryan Lerch wrote:
> On 12/05/2014 03:33 AM, Bastien Nocera wrote:
> >
> >----- Original Message -----
> >>With the creation of the 3 Fedora flavours, the process of tracking bugs
> >>and RFE's for Fedora workstation is a lot more muddled than it already
> >>is. Should this be something that we should focus on as a meta-task for
> >>the F22 release?
> >>
> >>Bugzilla currently tracks issues on a per-package (component in the
> >>Bugzilla terminology ) basis, so some packages are used in all 3
> >>flavours, but others are more specific to Workstation (e.g.
> >>gnome-shell). And some of these have a lot of bugs in the NEW status
> >>(gnome-shell has over 830).
> >Regarding that specifically, the Red Hat Bugzilla's performance makes
> >it unusable for anything but looking at one single bug. Triaging bugs
> >is a good way to waste weeks of time, and gain close to nothing.
> >
> >Cheers
>
> That is all well and good, but it doesn't really help us solve the issue
> that users are filing bugs, and some of them may be useful feedback and
> ideas on improving Fedora Workstation, but they are just sitting there.
>
> Any thoughts on how we can make this better for our users?
>
> I have started a triage attempt on the gnome-shell bugs to try to weed out
> some of the older ones that no longer apply, 847 left to go :)
BTW there should be easy ways to filter the set -- like separating
crashes out from other bugs. I'm not saying we should ignore crashes,
but the filter helps if you're trying to look for more general
feedback or ideas.
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=gnome-shell&f1=status_whiteboard&list_id=3067434&n1=1&o1=substring&product=Fedora&query_format=advanced&v1=abrt_hash&version=20&version=21&version=rawhide
** OR: http://ur1.ca/izz9a
[non-ABRT gnome-shell bugs for F20, F21, rawhide: 224]
Bastien's right that triage takes a lot of time, especially with a
slow BZ. But would it be possible to sort these bugs into a few
general bins? Examples: a11y, video issues, performance, etc.? The
purpose would be to see if one area seems to attract more feedback or
complaints than others, and that might help with F22 prioritization.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
More information about the desktop
mailing list