Houston, we have liftoff.
CCing eroyf by request.
CCing arch teams for review. Yes, I know documentation probably your least favorite thing to wade through, but I've finished up phase 1 of the handbooks, so I'd like you to review the changes made to the handbooks in http://www.gentoo.org/doc/en/handbook/draft/; if you want to view CVS sources, look in gentoo/xml/htdocs/doc/en/handbook/draft/ . Note that the networkless handbooks haven't been started yet, but I could use some feedback on what needs changing from 2006.1 as well. Please leave your notes and/or patches for me ASAP; the sooner I can get all this done, the better. Release is a-comin' up! :) MIPS/eroyf especially -- what about baselayout for you guys? bug 158637 will affect whether or not I can move you guys over to the new TIMEZONE format in conf.d/clock. Thanks, everyone!
According to codeman, we have some localized GLI: "So far I have de,fi,fr,hu, and spanish coming." We noticed that the accentuated characters required the loading of a console font. For example, one has to load "lat9u-16" to properly see the french instructions in the console. I found a link (http://linuxreviews.org/gentoo/i18n/) that helped me to believe these fonts have to be loaded by users: fr -> lat9u-16 de -> lat9u-16 fi -> lat9u-16 hu -> lat2u-16 es -> lat9u-16 If there are translations of the 2007.0 handbook for those languages, I suggest to add a sentence at the very beginning of hb-install-gli-dialog.xml to ask the user to load the console font. nightmorph: I suggest you to add a comment in the original english document, pointing to this bug. The addition could be: <p> We provide a french version of the Installer. To use it, just configure the "lat9u-16" font and set the LANG environment variable. </p> <pre caption="Run the french Gentoo Linux Installer"> # <i>sed -i s/default8x16/lat9u-16/ /etc/conf.d/consolefont</i> # <i>/etc/init.d/consolefont start</i> # <i>export LANG=fr_FR.utf8</i> # <i>installer</i> </pre> Note: I tested with a 2006.1 livecd, starting consolefont also starts keymap. But the keymap config is set to "us", whatever you choose in the "dokeymap" choice. So starting consolefont put back your keyboard in US mapping.
(In reply to comment #3) > fr -> lat9u-16 > de -> lat9u-16 > fi -> lat9u-16 > hu -> lat2u-16 > es -> lat9u-16 What about lat1-16, which is what we're currently loading on 2007.0? > Note: I tested with a 2006.1 livecd, starting consolefont also starts keymap. > But the keymap config is set to "us", whatever you choose in the "dokeymap" > choice. So starting consolefont put back your keyboard in US mapping. This is actually a genkernel bug which I think has since been fixed.
(In reply to comment #4) > (In reply to comment #3) > > fr -> lat9u-16 > > de -> lat9u-16 > > fi -> lat9u-16 > > hu -> lat2u-16 > > es -> lat9u-16 > > What about lat1-16, which is what we're currently loading on 2007.0? Would it mean that characters from latin9 can't be used, and latin1 replacements must be used instead? In that case Finnish translation would have suboptimal orthography in some corner cases, but nothing unbearable. AFAIK same'd go for French. However, latin2 and latin9 aren't really interchangeable. But I've also heard that there's some Chinese translation on its way, surely it would require a proper Unicode font to work.
(In reply to comment #5) > (In reply to comment #4) > > > > What about lat1-16, which is what we're currently loading on 2007.0? > > Finnish translation would have > suboptimal orthography in some corner cases, but nothing unbearable. AFAIK > same'd go for French. The *current* French translation is fine with lat1-16. What about using lat9u-16 as the default? > But I've also heard that there's some Chinese translation on its way, surely it > would require a proper Unicode font to work. I've no idea if a such *console* font ever exist.
Cosmetical issues: 1) You use " -- " as dash, which is not common in English printing...normally "---" without spaces is used, HTML has a representation in — which should be used. Even " - " is used as dash in some documents (did not patch those). 2) From-To expessions as "pages 2 - 11" are set as "pages 2--11" (-- = &ndash).
Could ARCH teams please review the profiles table at http://www.gentoo.org/doc/en/gentoo-upgrading.xml#doc_chap2 and let us know what needs to be changed. If upgrading to a 2007.0 profile needs more than a new symlink, please explain what needs to be done, see chapter below table. Thanks.
sparc64 2007.0: We don't support 2.4 kernels any longer except for previous profiles, so there's no 2007.0/2.4. Also 2007.0 profiles moved to gcc4 so the gcc upgrade guide should be followed when switching.
(In reply to comment #9) > sparc64 2007.0: > We don't support 2.4 kernels any longer except for previous profiles, so > there's no 2007.0/2.4. > Also 2007.0 profiles moved to gcc4 so the gcc upgrade guide should be followed > when switching. All sparc 2.4 instructions removed from the handbooks; only thing left is the upgrading guide. Also, if there's time, the partition layout for Sparc should be simplified to just root (/) and swap; the previous multi-partition layout was for sparc32, which is unsupported.
Adding a baselayout stable bug...this affects whether or not we have the new TIMEZONE in conf.d/clock method of setting timezone, or if MIPS is still stuck with the old deprecated cp /usr/foo method for this release.
Ehh... I don't have the new baselayout in for MIPS. In fact, there's tons of stuff that wasn't done for MIPS. If we need to pull in anything into the snapshot for MIPS, I need to know about it today.
Created attachment 118087 [details, diff] gentoo-upgrading.xml.patch Here are the changes to the profiles stuff in gentoo-upgrading.xml; I've heard back from some of the arch teams, but please review the list of profiles to verify that the right ones are supported or unsupported/should be removed. Also, I added a section on upgrading to 2007.0 that's mostly identical to 2006.1, except that now most arches have desktop and server subprofiles. Arch teams. please review and comment. GDP status report: with the exception of the upgrading guide, the liveusb guide testing & update, and our quickinstall/FAQs (minor updates needed for dir_index etc.), all the docs are complete to the best of my knowledge. At least, my checklists seem to be completed. ;)
(In reply to comment #13) > Created an attachment (id=118087) [edit] > gentoo-upgrading.xml.patch How about we stopped listing every profile and their sub-profiles for every release and told people to use `eselect profile list` and `eselect profile set #`?
(In reply to comment #14) > (In reply to comment #13) > > Created an attachment (id=118087) [edit] > > gentoo-upgrading.xml.patch > > How about we stopped listing every profile and their sub-profiles for every > release and told people to use `eselect profile list` and `eselect profile set > #`? > I'm in favor of this, as it makes maintaining the document easier. We might still want to include one of the symlink examples though, just in case users want to use a profile that eselect isn't showing. For example, (and I hope this isn't a bug), there's a server/ subprofile listed in amd64/2007.0/, but eselect profile list doesn't pick it up; only the desktop/ and no-multilib/ subprofiles are shown. I'll see about revising the document for this release. (Possibly the last release too; just keep the stuff about baselayout and Unicode, as otherwise 2007.0 and 2006.1 are identical).
Status report: Everything, and I mean *everything* to the best of my knowledge, is ready to go. It's all sitting in my local CVS. The only thing that still needs doing is the liveUSB guide, but neysx has that bug. Note: If I have the time, I'll rewrite that damn sh*tty Sparc quickinstall guide -- I do have a few changes that will show up at release time. Also, we need to re-evaluate the non-x86 quickinstall guides and FAQs too; bring them into line with proper coding style and up-to-date information, as well as making them more resemble the current "standard", which are the x86 quickinstall guides. * * * Release should have happened an hour ago I guess, but nothing's been sent my way from robbat2 or wolf31o2 yet. Soon as I know, I'll commit the stuff. There are lots more changes to everything in /doc/, including significant additions to metadoc.xml (if I break it, it's really rane's fault! :)) -- so if you can avoid it, please don't make any docs commits for about 12 hours (at least not to anything handbook or installation-related; ping me if you do). Maybe up to 24 hours, though hopefully I'll make all the commits 3 hours from now or less. Release time is almost here!
Docs are done and in CVS (and viewable live on www.gentoo.org). Hopefully I didn't forget anything important. Did metadoc and the index(es). Did (hopefully) all or most of the docs affected by all the release stuff in /doc/en/ too; will work on the quickinstall and FAQs later. All that's left now is bug 173117, which is being handled by our fearless leader. Thanks to everyone who helped out; closing this bug as we are *done*. PS: remember to mark any release bugs as RESO INVALID, as our handbooks are of course PERFECT in every aspect. ;) (just kidding of course....right?)
