@philinux
tracking unstable GNOME is taking lot of resources that we don't invest in our desktop (packaging a new stack every 3 weeks, dealing with transitions, regressions, etc)
That should not be new to the developers, they have been tracking Unstable Gnome for quite a few years now. News are that they are now using a lot of resources patching and tweaking the gnome components to meet Unity's needs, leaving much less resources to track unstable Gnome.
our desktop is quite less "stock GNOME" than it used to be, which means we have extra integration work to do and it's less trivial to do those "on the way" during the cycle
Same as the above, Ubuntu is using too many resources on 'extra integration work' because it's lesser stock Gnome.
GNOME unstable series and Ubuntu "working every day" are hard to conciliate goals
Yes of course, it's like riding two horses going in each their own direction (I posted that earlier on this thread). Either you follow Gnome or You fork the needed components and make your own Unity DE. But Ubuntu doesn't seem to have the resources to do so ?
GNOME is not communicating early enough on what is coming for us to discuss next cycle at UDS (see nautilus 3.6 in quantal)
Well Gnome is going through a lot of changes itself so thats not gonna happen before Gnome3 development calms down later in the release cycle, but that was the same with the changes from Gnome1 series to Gnome2 and should be expected in such big change from one series to another. Changes not known at UDS cannot be communicated.
GNOME is shipping stables with transitions half done (see gstreamer 1.0 this cycle) which is not something we want in Ubuntu
Outch ! that one you can blame on Gnome :biggrin:
our "feedback loop" with GNOME is not really working nowadays, they don't have time to look at most bugs and we hit regressions and sit on them until somebody on our side has time to look at them, which means neither GNOME or us benefits much from tracking unstable GNOME...
I am really sad if that's the whole truth, but I guess that's the kinda reaction you get when you expect cooperation from someone that feels your are trying to control and limit their developer freedom.
Cheers ;-)