Hello,

I'm sure that you all have heard of the new GNOME 2.12 release scheduled 
for September 7th.

The GNOME herd has been working furiously these past few weeks to bring 
the latest Release Candidate 1 to you for testing!

Heres a link to one person's review, if you'd like to see what's new:
http://www.gnome.org/~davyd/gnome-2-12/

If you would like to help us find bugs in this release, please unmask all 
packages located in the GNOME 2.12 section of package.mask.  Also, these 
need to be placed in package.keywords.  I've posted 
package.unmask, package.keywords, and instructions to ease testing at:
http://dev.gentoo.org/~allanonjl/gnome/2.12_rc/

The gnome-2.12_rc1.ebuild should hit the mirrors shortly. ( just committed 
)

We already have a tracker set up, it's:
http://bugs.gentoo.org/show_bug.cgi?id=103197

If you find a bug, please assign the bug to [EMAIL PROTECTED], and then add 
103197 as a blocker for your bug. ( Of course, after you search :) )

We also have a new tracking page that has helped us with this release ( 
and the official release soon ):
http://dev.gentoo.org/~allanonjl/gnome/gnome_status.html

Some changes that may be useful to note:
* mozilla is no longer a requirement for GNOME since epiphany can compile 
against firefox
* local use flag 'firefox' added for totem
* local use flag 'firefox' added for evolution-data-server

Some last minute bugs that were just committed ( may be a little bit 
before they hit the mirrors ):
* evolution-data-server must be compiled +ldap +kerberos in order for 
libexchange-storage module to be built for evolution-exchange
* gnome-desktop dependency in gnome-panel bumped to the 2.11.x version

Special thanks go to ka0ttic for keeping the c++ bindings up to date and, 
of course, everyone in the GNOME herd for the hard work so far.

We are aiming to move the official GNOME 2.12 release out of package.mask 
( and into unstable ) around September 14th.

Thanks, and happy bug hunting!

John N. Laliberte ( AllanonJL )
-- 
gentoo-dev@gentoo.org mailing list

Reply via email to