Comment 3 for bug 1219486

Revision history for this message
Jeremy BĂ­cha (jbicha) wrote :

1. GNOME 3.8 has only been tested with gnome-settings-daemon 3.8 and there's no guarantee that things work correctly when we mix and match pieces.
2. Since we did the gsettings-desktop-schemas update, there are gsettings keys that won't actually do anything without the updated gnome-settings-daemon backend. Even without doing the gnome-control-center 3.8 update, it would be nice for GNOME users to be able to tweak some of the new settings in dconf-editor at least.
3. We need to update this cycle because we need to fix bug 1201679 which is a High priority regression in Unity (GNOME was unaffected).
4. There are numerous other fixes and improvements if you read through the NEWS file. The update isn't just GNOME dropping Fallback support and we've patched back in the fallback pieces that Unity currently needs.
5. Tim did a lot of work on this update with the assumption that it could make it into Saucy. We were delayed several weeks by indicator-keyboard taking longer to land than expected. I tried to help indicator-keyboard along as well as I could and complained that the longer the delay, the more difficult it would be to land gnome-settings-daemon 3.8 by Feature Freeze.

There was one final regression that Tim fixed over the weekend. Ubuntu GNOME shouldn't be penalized for taking care not to cause regressions and waiting for Unity work.

I've been running Unity all weekend to make sure that the update didn't cause any new problems. Many people have installed the GNOME3 Staging PPA; some of those people use Unity.