Re: Blocker bug review for 3.8

2013-03-06 Thread Javier Jardón
On 5 March 2013 22:15, Ray Strode halfl...@gmail.com wrote: I don't have a problem making it build time optional configure switch for 3.8 and then moving it to a separate git module for 3.10 If you dont mind the extra work, I think this is the best solution (and set to not build the simple

Re: Blocker bug review for 3.8

2013-03-05 Thread Piñeiro
On 03/05/2013 05:57 AM, Matthias Clasen wrote: One the eve of 3.7.91, here is a summary of the list of open bugs currently marked as 3.8 blocker. This list has 32 bugs on it today. That may sound a lot, but keep it in perspective: we've already closed 113 bugs that were marked as 3.8 blocker.

Re: Blocker bug review for 3.8

2013-03-05 Thread Jeremy Bicha
On 4 March 2013 23:57, Matthias Clasen matthias.cla...@gmail.com wrote: * related to feature 'drop fallback mode / add classic mode': 688665 gdm drop gdm fallback session Given that drop fallback mode is an anti-feature, I have a hard time considering that bug as a 3.8 blocker. It sounds

Re: Blocker bug review for 3.8

2013-03-05 Thread Justin Joseph
On 5 March 2013 19:49, Jeremy Bicha jbi...@ubuntu.com wrote: this makes it very difficult for us to ship the latest GNOME promptly in Ubuntu I thought ubuntu is shipping 3.6 this cycle and ubuntu gnome already dropped fallback?? * Thanks,* Justin

Re: Blocker bug review for 3.8

2013-03-05 Thread Matthias Clasen
On Tue, Mar 5, 2013 at 9:19 AM, Jeremy Bicha jbi...@ubuntu.com wrote: On 4 March 2013 23:57, Matthias Clasen matthias.cla...@gmail.com wrote: * related to feature 'drop fallback mode / add classic mode': 688665 gdm drop gdm fallback session Given that drop fallback mode is an

Re: Blocker bug review for 3.8

2013-03-05 Thread Jeremy Bicha
On 5 March 2013 10:46, Matthias Clasen matthias.cla...@gmail.com wrote: If you want to keep fallback mode alive, I suggest getting engaged in building that right place - this bug has been on the 3.8 blocker list since before Xmas, so it is not exactly news that we were going to do this... You

Re: Blocker bug review for 3.8

2013-03-05 Thread Jasper St. Pierre
What's the specific freeze break? Dropping the simple-greeter from gdm? Dropping gnome-panel, etc. from the official module set? We're not in hard code freeze yet, and neither of these are UI freeze breaks, as far as I understood it. On Tue, Mar 5, 2013 at 12:44 PM, Jeremy Bicha

Re: Blocker bug review for 3.8

2013-03-05 Thread Jeremy Bicha
On 5 March 2013 13:13, Jasper St. Pierre jstpie...@mecheye.net wrote: What's the specific freeze break? Dropping the simple-greeter from gdm? Dropping gnome-panel, etc. from the official module set? We're not in hard code freeze yet, and neither of these are UI freeze breaks, as far as I

Re: Blocker bug review for 3.8

2013-03-05 Thread Ray Strode
Hi, On Tue, Mar 5, 2013 at 1:31 PM, Jeremy Bicha jbi...@ubuntu.com wrote: Dropping the simple greeter from gdm breaks feature freeze. Removing a feature is even more disruptive than adding a feature so I thought it was understood that we shouldn't be doing these changes after feature freeze

Blocker bug review for 3.8

2013-03-04 Thread Matthias Clasen
One the eve of 3.7.91, here is a summary of the list of open bugs currently marked as 3.8 blocker. This list has 32 bugs on it today. That may sound a lot, but keep it in perspective: we've already closed 113 bugs that were marked as 3.8 blocker. Any help with getting the remaining 32 bugs fixed

Re: Blocker bug review for 3.8

2013-03-04 Thread Florian Müllner
On Mar 5, 2013 5:57 AM, Matthias Clasen matthias.cla...@gmail.com wrote: 694771 mutter menus broken in 3.7.10 This was fixed in 3.7.91, somehow we missed closing the bug. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org

Re: Blocker bug review for 3.8

2013-03-04 Thread Claudio Saavedra
On Mon, 2013-03-04 at 23:57 -0500, Matthias Clasen wrote: * related to gnome goal: libsecret migration: 679918 epiphanylibsecret migration I was waiting on a libsecret release, but I've finally merged the secret-migration to master and this bug is fixed. Claudio