Hi Matt,
On Thu, Apr 14, 2011 at 10:41:23AM -0500, Matthew Summers wrote: > 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 problem is that the date is still subject to change. If we get more bugs that we think should block stabilization, those would be fixed, then a new release put out, then we are back to waiting 30 days unless we make an exception to the 30 day rule. > 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. As far as I know, the only thing that can go wrong here is rebooting after installing bl2/openrc without following the migration guide. If you do that, the only thing you can do is boot a live cd, chroot into the system and follow the migration guide from there. There's not really a way I know of that we could write a script to do that. > 3. Update the handbook to reflect these changes as soon as possible, > and have that all go public simultaneously with the stabilization. There is a bug that is blocked by the tracker for this. > 4. I have attached an edited and unfinished version of the original > news item for review. I attempted to be succinct. Ok, I took your news item, and I'll look it over. I may add more to it about what will happen if you do not follow the migration guide.
pgphF1gkzJGmd.pgp
Description: PGP signature
