On 09/30/2009 08:07 AM, William Jon McCann wrote: [...] If the update needs a restart, I *never* do it right away: I started the computer because I have things to do with it, not waste a couple of minutes with a reboot.

On 09/30/2009 12:27 PM, drago01 wrote: > On Wed, Sep 30, 2009 at 10:39 AM, Nicu Buculei <nicu_fedora(a)nicubunu.ro&gt; wrote: >> On 09/30/2009 08:07 AM, William Jon McCann wrote: >> [...] >> If the update needs a restart, I *never* do it right away: I started the >> computer because I have things to do with it, not waste a couple of >> minutes with a reboot. > > Exactly I never reboot just because PK tells me "please reboot". Well, never was a bit too strong... the system may get acting so weird so ultimately you *have* to reboot :p

On Wed, Sep 30, 2009 at 7:07 AM, William Jon McCann <william.jon.mccann(a)gmail.com&gt; wrote: > Hi, > > Since it has come up recently, I figured I'd briefly mention that some > people in the desktop team, QE, and release engineering had a few > lunchtime chats about our update process.  I tried to write down some > of what we talked about: > https://fedoraproject.org/wiki/Desktop/Whiteboards/UpdateExperience > > I later found out that there are a number of different initiatives > underway that may help with this problem.  So, that is good news. > > Interested to hear your thoughts. "#  System updates must fix critical bugs or security vulnerabilities only " Well there should be one exception for this: Adding support for new hardware (ie. kernel rebase). The reason is that if we don't do that the user have to either wait until the next release to be able to use the his/her hardware or go googling for how to compile the specifi driver by hand. Both aren't really a great user expirence.

On 09/30/2009 10:37 AM, William Jon McCann wrote: > Hi, > > Since it has come up recently, I figured I'd briefly mention that some > people in the desktop team, QE, and release engineering had a few > lunchtime chats about our update process.  I tried to write down some > of what we talked about: > https://fedoraproject.org/wiki/Desktop/Whiteboards/UpdateExperience > > I later found out that there are a number of different initiatives > underway that may help with this problem.  So, that is good news. > > Interested to hear your thoughts. One thing I would really like is for PackageKit to download updates in the background (detecting whether I am on a low bandwidth connection) and only prompt me for updates when it is ready to install. Another constant annoyance is that soon after a yum operation in the command line, PackageKit insists on updating some metadata immediately thereby locking out the subsequent commands for sometime (can be a considerable delay). I would prefer it to wait for a few mins and not interrupt me. Filed and closed WONTFIX however.

2009/9/30 Rahul Sundaram : > One thing I would really like is for PackageKit to download updates in > the background (detecting whether I am on a low bandwidth connection) > and only prompt me for updates when it is ready to install. It already detects what kind of connection you are on. When the idle-bandwidth changes are done we can do things like this without upsetting people actually using the connection.

> Another constant annoyance is that soon after a yum operation in the > command line, PackageKit insists on updating some metadata immediately > thereby locking out the subsequent commands for sometime (can be a > considerable delay). I would prefer it to wait for a few mins and not > interrupt me. Filed and closed WONTFIX however. Sure, remove PackageKit-yum-plugin or blacklist it in the yum configuration. There's also now configuration for this value in the systemwide config file, /etc/PackageKit/PackageKit.conf: