| 1 |
On Sat, Nov 26, 2011 at 2:13 AM, Nirbheek Chauhan <nirbheek@g.o> wrote: |
| 2 |
> Since GNOME 3 is already in the |
| 3 |
> tree, and the news file content is straightforward, I'd like to commit |
| 4 |
> this in 24hrs if there are no problems. |
| 5 |
|
| 6 |
If we're gong to go to all the trouble to create upgrade guides and |
| 7 |
news/etc, wouldn't it make sense to send out the news item a few days |
| 8 |
BEFORE making the change? |
| 9 |
|
| 10 |
If a user runs emerge -u world daily they wouldn't even see this news item. |
| 11 |
|
| 12 |
Obviously the horses have already left the barn, but maybe this is |
| 13 |
something we can do differently when it comes time to stabilize the |
| 14 |
change? |
| 15 |
|
| 16 |
I'm sure this was inadvertent, but looking beyond just this particular |
| 17 |
incident is there anything we can do to improve our use of news items? |
| 18 |
Since we're a distro that uses rolling releases users really have no |
| 19 |
way to know what to expect after any particular emerge world. It |
| 20 |
could be some completely routine bump that isn't going to cause |
| 21 |
problems, or it could require extensive rebuilding, config-file |
| 22 |
tweaking, and risk of the system not booting. News is really the only |
| 23 |
way to give them a heads-up in advance. Granted, something like a |
| 24 |
gnome/kde bump is going to pull in so many packages that I think most |
| 25 |
users would exercise caution, so that mitigates the issue a bit. |
| 26 |
|
| 27 |
Rich |
Archives