Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: Nirbheek Chauhan <nirbheek@g.o>
Cc: Gentoo Dev <gentoo-dev@l.g.o>, pr@g.o, gnome <gnome@g.o>
Subject: [gentoo-dev] Re: RFC: Gentoo News file about GNOME 3.2's unmasking
Date: Sat, 26 Nov 2011 12:26:51
In Reply to: [gentoo-dev] RFC: Gentoo News file about GNOME 3.2's unmasking by Nirbheek Chauhan
On Sat, Nov 26, 2011 at 2:13 AM, Nirbheek Chauhan <nirbheek@g.o> wrote:
> Since GNOME 3 is already in the > tree, and the news file content is straightforward, I'd like to commit > this in 24hrs if there are no problems.
If we're gong to go to all the trouble to create upgrade guides and news/etc, wouldn't it make sense to send out the news item a few days BEFORE making the change? If a user runs emerge -u world daily they wouldn't even see this news item. Obviously the horses have already left the barn, but maybe this is something we can do differently when it comes time to stabilize the change? I'm sure this was inadvertent, but looking beyond just this particular incident is there anything we can do to improve our use of news items? Since we're a distro that uses rolling releases users really have no way to know what to expect after any particular emerge world. It could be some completely routine bump that isn't going to cause problems, or it could require extensive rebuilding, config-file tweaking, and risk of the system not booting. News is really the only way to give them a heads-up in advance. Granted, something like a gnome/kde bump is going to pull in so many packages that I think most users would exercise caution, so that mitigates the issue a bit. Rich


Subject Author
[gentoo-dev] Re: RFC: Gentoo News file about GNOME 3.2's unmasking Nirbheek Chauhan <nirbheek@g.o>