Bug#610656: Drop proposed-updates from "what's new"

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

Package: release-notes

Hi,

The text in the proposed-updates section of whats-new.dbk indicates that
it is not really a new feature for lenny and was included to raise
awareness.  If it served that purpose then there's no need to carry it
forward for the squeeze RN; if it didn't then I'm not convinced that
continuing to include it will bring much benefit.

Attached is a patch to remove the section in its entirety; -release
X-D-CCed in case anyone has objections / better ideas.

Regards,

Adam

commit ff959e9a384656f144434db42c9624ca2a50e38a
Author: Adam D. Barratt <adam@adam-barratt.org.uk>
Date:   Thu Jan 20 19:48:15 2011 +0000

    Drop discussion of proposed-updates from "what's new"
    
    Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
    
    The information included in the section was already marked as "not
    really new" for lenny.

diff --git a/en/whats-new.dbk b/en/whats-new.dbk
index cedb274..2a2ff3c 100644
--- a/en/whats-new.dbk
+++ b/en/whats-new.dbk
@@ -505,45 +505,6 @@ configuration file.
   </para>
 </section>
 
-<section id="proposed-updates-intro">
-  <title>The proposed-updates section</title>
-  <para>
-    All changes to the released stable distribution (and to oldstable)
-    go through an extended testing period before they are accepted
-    into the archives.  Each such update of the stable (or oldstable)
-    release is called a point release. Preparation of point releases
-    is done through the <literal>proposed-updates</literal> mechanism.
-  </para>
-  <para>
-    Packages can enter <literal>proposed-updates</literal> in two
-    ways. Firstly, security-patched packages added to security.debian.org are
-    automatically added to <literal>proposed-updates</literal> as well.
-    Secondly, &debian; developers may upload new packages to
-    <literal>proposed-updates</literal>, where they get added after review by
-    the Stable Release Managers. The current list of packages can be seen at
-    <ulink
-    url="&url-ftpmaster;/proposed-updates.html">&url-ftpmaster;/proposed-updates.html</ulink>.
-  </para>
-  <para>
-    If you wish to help test updates to packages before they are
-    formally added to a point release, you can do this by adding the
-    <literal>proposed-updates</literal> section to your
-    <filename>sources.list</filename>:
-  </para>
-  <programlisting>deb     &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib
-deb-src &url-debian-mirror-eg;/debian &releasename;-proposed-updates main contrib</programlisting>
-  <para>
-    The next time you run <command>apt-get update</command>, the
-    system will become aware of the packages in the
-    <literal>proposed-updates</literal> section and will consider them
-    when looking for packages to upgrade.
-  </para>
-  <para>
-    This is not strictly a new feature of Debian, but one that has not
-    been given much exposure before.
-  </para>
-</section>
-
 <section id="stable-updates">
   <title>The stable-updates section</title>
   <para>