[release-notes] Some copy on the pre-release testing process, and hints on helping with RNs

[Pete Travis]

commit 2ec3566c25d938fa948da54b13b4568a0f3887e4
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Aug 30 11:32:58 2014 -0600

    Some copy on the pre-release testing process, and hints on helping with RNs

 en-US/Release_Notes.xml |    2 +-
 en-US/prerelease.xml    |   57 +++++++++++++++++++++++++++++++++++-----------
 2 files changed, 44 insertions(+), 15 deletions(-)
---
diff --git a/en-US/Release_Notes.xml b/en-US/Release_Notes.xml
index e009349..37a533d 100644
--- a/en-US/Release_Notes.xml
+++ b/en-US/Release_Notes.xml
@@ -13,7 +13,7 @@
   <xi:include href="Section-Welcome.xml" 
 	      xmlns:xi="http://www.w3.org/2001/XInclude" />
 
-  <xi:include href="pre-release.xml" 
+  <xi:include href="prerelease.xml" 
         xmlns:xi="http://www.w3.org/2001/XInclude" />
 
   <!--<xi:include href="Section-Sysadmin.xml" 
diff --git a/en-US/prerelease.xml b/en-US/prerelease.xml
index ce8f41a..8ebcb7b 100644
--- a/en-US/prerelease.xml
+++ b/en-US/prerelease.xml
@@ -88,19 +88,48 @@
     <para>
       EOL releases <emphasis>do not receive security updates</emphasis> or bug fixes.  Community support venues such as the <ulink url="https://lists.fedoraproject.org/pipermail/users/">Users mailing list</ulink> or <ulink url="https://fedoraproject.org/wiki/Communicating_and_getting_help#IRC_for_interactive_community_support">IRC channels</ulink> do not assist with issues on EOL systems.  You should update your system before it reaches EOL.
     </para>
-        
-
-
-         
-
-    
-
-
   </section>
+  <section id="how_to_test">
+    <title>Testing Fedora Pre-releases</title>
+    <para>
+      Testing of Fedora Pre-releases is performed by the <ulink url="http://fedoraproject.org/wiki/QA">Fedora Quality Assurance</ulink> group.  If you are testing Fedora &PRODVER; Alpha or Beta and providing feedback, you are part of the QA Team!
+    </para>
+    <para>
+      There are several places to provide your feedback and follow along with testing efforts:
+      <simplelist>
+        <member>
+          <emphasis>Fedora Testing mailing list</emphasis> - https://lists.fedoraproject.org/mailman/listinfo/test
+        </member>
+        <member>
+          <emphasis>Fedora QA IRC Channel</emphasis> - #fedora-qa on Freenode
+        </member>
+        <member>
+          <emphasis>Blocker Bug Tracking Application</emphasis> - https://qa.fedoraproject.org/blockerbugs
+        </member>
+        <member>
+          <emphasis>Bugzilla</emphasis> - https://bugzilla.redhat.com
+        </member>
+      </simplelist>
+    </para>
+    <para>
+      Refer to the instructions at <ulink url="http://fedoraproject.org/wiki/How_to_file_a_bug_report" /> for guidance on filing an effective bug report.
+    </para>
+  </section>
+  <section id="release-notes-feedback">
+    <title>Pre-Release Release Notes</title>
+    <para>
+      The Fedora Release Notes are under active development during the pre-release stages of the release cycle.  The current copy is maintained on the wiki under <ulink url="https://fedoraproject.org/wiki/Category:Documentation_beats" /> until the Beta release, when they are moved into a public git repository and processed for presentation and distribution.
+    </para>
+    <para>
+      If you are testing the Alpha release of Fedora and encounter notable changes, you can help improve the Release Notes by adding to the <ulink url="https://fedoraproject.org/wiki/Category:Documentation_beats">appropriate beat</ulink>. Don't worry too much about presentation or writing ability; the Docs team will appreciate your help in identifying changes and can refine the copy further.
+    </para>
+    <para>
+      During the Beta release or at any time during the release cycle, you can file a bug against the Release Notes.
+    </para>
+    <para>
+      You can mail the Fedora Docs mailing list to provide feedback on the Release Notes or any Fedora documentation.
+    </para>
+  </section>
+</section>
 
-  points:
-  - the point is testing, not preview
-  - work with QA, here's how
-  - how to file a bug
-  - release notes are WIP, here's where
-  
+