Seems like a fine idea if the release engineering people actually use it
and the overhead to maintain it isn't excessive.
It would be nice to eliminate the "nice to have" in a different sense
bug trackers - like F15Target (which isn't currently blocking anything)
to prevent confusion and wasted ef
On 09/18/2010 08:22 PM, Adam Williamson wrote:
> On Sat, 2010-09-18 at 18:45 +1000, Steven Haigh wrote:
>> I'd like to see these as nice-to-be-fixed bugs before F14 - otherwise
>> F13 will be a more polished release than F14 imho...
>>
>> Bluetooth always disabled on startup
>> https://bugzilla.red
On Sat, 2010-09-18 at 18:45 +1000, Steven Haigh wrote:
> I'd like to see these as nice-to-be-fixed bugs before F14 - otherwise
> F13 will be a more polished release than F14 imho...
>
> Bluetooth always disabled on startup
> https://bugzilla.redhat.com/show_bug.cgi?id=634205
That's on the list a
I'd like to see these as nice-to-be-fixed bugs before F14 - otherwise
F13 will be a more polished release than F14 imho...
Bluetooth always disabled on startup
https://bugzilla.redhat.com/show_bug.cgi?id=634205
ghostscript error printing PDF with image.
https://bugzilla.redhat.com/show_bug.cgi?i
Hi, everyone. I'd just like to point up a new process we just put in
place: tracking nice-to-have bugs for pre- and final releases.
Sorry not to have proposed this on the list, but I wanted to try and get
it done for the Beta so I just went ahead and put it in. The idea is to
track bugs that aren'
