public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthew Summers <quantumsummers@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: William Hubbs <williamh@gentoo.org>
Subject: Re: [gentoo-dev] Re: openrc portage news item
Date: Thu, 14 Apr 2011 10:41:23 -0500	[thread overview]
Message-ID: <BANLkTiks-6eCsnqWN6RyQ_Ta+hKkm5LmdA@mail.gmail.com> (raw)
In-Reply-To: <4DA70861.1060909@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Hi,

I have a few suggestions regarding this major change to Gentoo systems.

1. We should determine and then announce the precise date (appears to
be in May) and time that baselayout-2 will be stabilized via:
  1.1 A front page News item on www.g.o (PR team assemble!),
  1.2 The main MLs (gentoo-announce, gentoo-users, etc),
  1.3 Add a link to the www news item to /topic in #gentoo, and
  1.4 Post a sticky topic in the Forum.
all in addition to the eselect news item under discussion here. The
above would link to the migration guide too.

The rationale for this effort at getting the word out is to prevent
users from hosing their system(s). While I tend to agree that users
should read these eselect news items, its often not the case.
Therefore I recommend shooting for the widest possible distribution of
this information. Also, this gives PR a chance to let the world know
about openrc and its benefits to Gentoo.

2. We should prepare a quick "recover-your-system" guide (could also
create a script too) that can be quickly linked to for user support.
This will save time for people providing support via IRC, email, etc,
and give people a reasonable means of system recovery without huge
pain.

3. Update the handbook to reflect these changes as soon as possible,
and have that all go public simultaneously with the stabilization.

4. I have attached an edited and unfinished version of the original
news item for review. I attempted to be succinct.

This is a really exciting and potentially also rather
anxiety-provoking change for our user base and Gentoo. We all know
that the new baselayout is awesome, and users will find out soon
enough. We simply need to make our best effort at easing the
transition so we minimize the number of casualties.

Thank you,
Matt
-- 
Matthew W. Summers

[-- Attachment #2: 2011-05-01-baselayout-update.en.txt --]
[-- Type: text/plain, Size: 877 bytes --]

Title: Baselayout update
Author: Christian Faulhammer <fauli@gentoo.org>
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2011-05-01
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-apps/baselayout-2

On May XX 2011, you will see an update for sys-apps/baselayout to
2.x and a new package, sys-apps/openrc. It is recommended that you
perform this update as soon as possible. Please note, it is
__Absolutely_Critical__ that you follow the steps outlined in the 
migration guide located at the following URL.
http://www.gentoo.org/doc/en/openrc-migration.xml

FAILURE TO FOLLOW THE MIGRATION GUIDE
CAN RESULT IN AN UNBOOTABLE SYSTEM!

For more information or supprt regarding this change please see the
following:
- link to news item (should contain info regarding where to obtain support)
- link to recover-system guide
- link to handbook

  reply	other threads:[~2011-04-14 15:42 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 18:15 [gentoo-dev] openrc portage news item William Hubbs
2011-04-13 18:27 ` Thomas Beierlein
2011-04-13 18:32 ` justin
2011-04-13 18:41 ` "Paweł Hajdan, Jr."
2011-04-13 19:58   ` William Hubbs
2011-04-14  8:09     ` [gentoo-dev] " Duncan
2011-04-14 11:44       ` Rich Freeman
2011-04-15 14:04       ` Peter Hjalmarsson
2011-04-15 19:01         ` Duncan
2011-04-13 19:56 ` [gentoo-dev] " William Hubbs
2011-04-14  5:30   ` justin
2011-04-14  7:21     ` Dirkjan Ochtman
2011-04-14  8:19       ` justin
2011-04-14  8:40       ` [gentoo-dev] " Duncan
2011-04-14 14:44         ` Dale
2011-04-14 15:41           ` Matthew Summers [this message]
2011-04-14 16:12             ` Dale
2011-04-14 18:48             ` William Hubbs
2011-04-14 10:32 ` [gentoo-dev] " Kfir Lavi
2011-04-14 10:32   ` Kfir Lavi
2011-04-14 10:51   ` Tomá? Chvátal
2011-04-14 11:03     ` Pacho Ramos
2011-04-14 11:21     ` Thomas Beierlein
2011-04-14 11:27       ` Sylvain Alain
2011-04-21  1:12   ` Donnie Berkholz
2011-04-21  2:23     ` Jeroen Roovers
2011-04-21  2:34       ` Jeroen Roovers
2011-04-22 10:39     ` Lars Wendler
2011-04-29 18:41       ` Brian Harring
2011-04-30  2:19         ` William Hubbs
2011-04-30  4:59           ` Brian Harring
2011-04-30  7:13             ` [gentoo-dev] " Duncan
2011-04-30 11:46               ` Brian Harring
2011-04-30 12:03                 ` Rich Freeman
2011-04-30 12:58                   ` Brian Harring
2011-04-30 13:06                     ` Jeremy Olexa
2011-04-30 13:40                       ` Brian Harring
2011-04-29  7:08 ` [gentoo-dev] " William Hubbs
2011-04-29 11:21   ` Rich Freeman
2011-04-29 11:28     ` Ciaran McCreesh
2011-04-29 17:18       ` Alex Alexander
2011-04-29 17:25         ` Ulrich Mueller
2011-04-29 17:32           ` Alex Alexander
2011-04-29 17:52           ` Rich Freeman
2011-04-29 17:58             ` Alex Alexander
2011-04-30  0:34               ` William Hubbs
2011-04-30  9:04                 ` Sergei Trofimovich
2011-04-30 12:41                 ` Roy Bamford
2011-04-29 14:27   ` [gentoo-dev] " Duncan
2011-05-01 19:12 ` [gentoo-dev] " William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BANLkTiks-6eCsnqWN6RyQ_Ta+hKkm5LmdA@mail.gmail.com \
    --to=quantumsummers@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=williamh@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox