release-notes README-en.xml,1.1,1.2
Jeremy Katz (katzj)
fedora-docs-commits at redhat.com
Wed Feb 15 19:25:19 UTC 2006
Author: katzj
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18613
Modified Files:
README-en.xml
Log Message:
some updates to the readme for accuracy for fc5 test3. this probably needs
actual eyes on it before fc5 final
Index: README-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/README-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README-en.xml 24 Oct 2005 13:13:33 -0000 1.1
+++ README-en.xml 15 Feb 2006 19:25:12 -0000 1.2
@@ -14,19 +14,19 @@
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
-<!ENTITY DISTROVER "4"> <!-- The software's version -->
+<!ENTITY DISTROVER "5 test3"> <!-- The software's version -->
]>
-<article id="index" lang="en" arch="x86;x86_64" os="test;final">
+<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; README</title>
<copyright>
- <year>2005</year>
+ <year>2006</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
<legalnotice id="legalnotice">
- <para>The contents of this CD-ROM are Copyright © 2005 &PROJ; and
+ <para>The contents of this CD-ROM are Copyright © 2006 &PROJ; and
others. Refer to the End User License Agreement and individual
copyright notices in each source package for distribution terms.</para>
@@ -85,6 +85,8 @@
| Core used by the installation process
|----> images -- boot and driver disk images
|----> isolinux -- files necessary to boot from CD-ROM
+ |----> repodata -- repository information used by the
+ | installation process
|----> README -- this file
|----> RELEASE-NOTES -- the latest information about this release
| of Fedora Core
@@ -126,7 +128,7 @@
<para>If you are setting up an installation tree for NFS, FTP, or HTTP
installations, you need to copy the <filename>RELEASE-NOTES</filename>
files and all files from the <filename>Fedora</filename> directory on
- discs 1-3. On Linux and Unix systems, the following process will properly
+ discs 1-5. On Linux and Unix systems, the following process will properly
configure the /target/directory on your server (repeat for each disc):</para>
<orderedlist>
@@ -210,7 +212,7 @@
properly authorized. The obligations under this paragraph shall survive
in perpetuity.</para>
</section>
-<!--
+
<section id="s1-test" os="test">
<title>README Feedback Procedure</title>
@@ -232,7 +234,7 @@
</listitem>
<listitem>
- <para><guilabel>Version:</guilabel> Not really important (I'm using
+ <para><guilabel>Version:</guilabel> "devel" </para>
"devel")</para>
</listitem>
@@ -251,37 +253,9 @@
what could be improved.</para>
</listitem>
- <listitem>
- <para><guilabel>Blocks:</guilabel> 114406 (The README blocker bug
- number)</para>
- </listitem>
</itemizedlist>
-
- <para>A quick way of seeing what sorts of bugs have been posted against the
- README is to look at the bugs listed in the <guilabel>Bug 114406 depends
- on:</guilabel> field of the &DISTRO; release notes blocker bug:</para>
-
- <para><ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406</ulink></para>
-
- <para>If you are interested in following the discussion of any of these
- bugs, feel free to add yourself to the bug's CC list. That way, you'll
- get email whenever there are any changes to the bug.</para>
-
- <para>As bugs are posted for the various parts of the README file,
- subsequent test versions of these release notes will contain links similar
- to this one:</para>
-
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408</ulink>
- %%%</remark>
-
- <para>These links point to Bugzilla entries for the information preceding
- the link. This makes it easier for people to contribute — just
- point your browser at the link, add your comments to the bug, and commit
- your changes.</para>
</section>
--->
+
<!--
<ackno>(
<emphasis arch="x86">x86</emphasis>
More information about the Fedora-docs-commits
mailing list