Shared publicly  - 
I've written a post about the cool stuff that's coming up in the next GNOME release. Check it out!
Michael Hill's profile photoZeeshan Ali's profile photoOlav Vitters's profile photoKjell Thomas Pedersen's profile photo
Ok, I'm sure I am not the first one to ask this, but:
Are there any plans to change Nautilus 3 UI for 3.4?
Ian Hex
Georgi... you need help.
+Georgi Karavasilev - arghhhh, I forgot to mention - Nautilus has got undo this cycle! You always miss something!

That aside, we're in UI freeze for 3.4 now, so there won't be any UI changes until next release.
Ok, thanks for the info :)
P.S. Izo, i was being kind here, I did not start my regular anti Nautilus 3 rant :D
so i guess the only distro to have all the features on gnome 3.4 will be fedora?
arch it is then. fedora is like a half assed seppuku. if i am going to kill myself, id rather do it in style.
+Kumar Aatish All GNOME distros will get GNOME 3.4; it just depends on how long you want to wait. Arch generally gets it first, then Ubuntu (~90%, use the GNOME 3 PPA for the remainder), and Fedora soon after, followed by openSUSE. I expect Debian Wheezy to include GNOME 3.4 too.
What? No mention of Mageia? In our "unstable" version (called Cauldron), we package GNOME release asap. My goal is to have simple tarball releases available to all Cauldron users within 1 hour (so 1 hour between upload of the tarball and a new package on the primary mirrors). Of course, it takes longer than that when there are new dependencies, new files, etc.
+Olav Vitters some of the GNOME documenters were using the Mageia betas when working on GNOME 3.4 documentation. Thanks for your work on GNOME in Mageia.
+Olav Vitters - further to +Jim Campbell's comment, Mageia's 3.4 was as steady as a rock throughout the hackfest while openSUSE was unbootable for a couple of days (admittedly only for people insisting on updating constantly).
I would testify to what +Olav Vitters said about Mageia. I was positively surprised to see how fast Boxes was packaged for Mageia.
+Jeremy Bicha: IMO, a lot of the packaging is somewhat boring. You just download the new tarball, verify it, increase the number in the spec file, reset the release number to 1, check if patches still apply, then commit all changes and submit the new spec file for building. I've automated that bit (triggered by ftp-release-list). If it builds successfully, it'll be available really quickly for Mageia Cauldron users. I know other distributions have a policy that things should be tested before uploading, but that is what we use Cauldron for. Further, anything on is often reliable anyway. Also, I don't do stable->unstable upgrades (initial change from GNOME 3.2 -> 3.3 is more manual on purpose). This is partly helped because Mageia packages libraries by their major version (e.g. lib64jpeg8-1.2.0-3.mga2 has /usr/lib64/ We can package a "libjpeg" with a new major (e.g. 9) and then gradually recompile things against the new libjpeg. Until everything is recompiled, both libjpeg packages are on the mirrors. There are also checks in place to ensure things get recompiled.

I'm trying to automate all the boring tasks. E.g. updating buildrequires, removing patches applied upstream, etc (still on the todo though).

Oh, and within Mageia we have maintainers (people responsible), but anyone can commit and submit a package. So if something bad happens, there will be a lot of people who can fix it quickly. There are also lots of people looking at every new package + spec change (very noticeable on the mageia-dev mailing list).
Problem is that most distros will somehow bastardize the Gnome 3 experience. Best to stick with the techy distros (like arch..) Been running Mint for a while, but sloooow to update and their hybrid approach in 12 didn't go well with me.
Add a comment...