Nice-to-have bug trackers

[Steven Haigh]

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.redhat.com/show_bug.cgi?id=634205
>
> That's on the list already.

Sweet :)

>> ghostscript error printing PDF with image.
>> https://bugzilla.redhat.com/show_bug.cgi?id=633848
>
> Mmmf...printing stuff can be handled fine with updates. One of the main
> guidelines for nice-to-have bugs that we have followed so far (without
> writing it down) is that mostly they're bugs which fix something that
> can't be fixed as an update - say, a bug in anaconda, or an X bug which
> stops you being able to install, or whatever.

I disagree strongly with this. I believe that when a final release is 
shipped that just about every common function should work. This includes 
mostly what is on the blockers list, but I also think items like 
networking, printing, gvfs etc, instant messaging (ie empathy) should be 
working and crash free.

The bug I have come across is with ghostscript itself - which is a major 
component that will break printing to *all* printers - not just a few or 
have a minor subset of printing. So far I have tested this bug on 4 
printers (both PS and PCL) and all have been affected. In my eyes, this 
means a major feature is broken - and we shouldn't ship until it is 
fixed. Seeing as this worked perfectly in F13 - this is a major regression.

>> --- Optional ---
>> NetworkManager does not handle bnep0 connections.
>> https://bugzilla.redhat.com/show_bug.cgi?id=633339
>
> That's really an enhancement request, it's not a bug per se. Did you
> know NM can configure Bluetooth DUN and PAN itself, though? You don't
> need to set up a connection manually and then have NM manage it. Check
> Dan's blog for details.

Yes, I've seen this - and to date it didn't quite click - but it seems 
when pairing I had to have the Internet Sharing application open on my 
phone for PAN to be detected. As there is no way to update the services 
on your BT device via gnome-bluetooth - I can't see what is available on 
my device to verify. It seems interesting that my normal way of starting 
the internet sharing from my phone and getting it to connect to the 
laptop is ignored by NM - so I have to initiate the connection via NM. 
Either way - I have a workaround now - so that at least makes me happier! :)

> I'd like to keep this thread about the process, though, not for
> discussing specific bugs.

Sorry, I must have misunderstood - however hopefully I have bridged the 
gap now between the process and these specific examples.

--
Steven Haigh

Email: netwiz at crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299