> Processing commands for cont...@bugs.debian.org:
>
>> # that paragraph is kept on purpose for this release in the hope that more
>> people will notice
>> tags 706529 + jessie
Aren't readers likely to see that "news item", recognise that it's
stale, and therefore skip over both that and the associated item on
backports (where the change is fairly subtle)?
Still, we could guard against that by reversing the order of the
sections... I attach a revised, reordered patch that just takes out
the line specifically mentioning "volatile".
> Bug #706529 [release-notes] release-notes: stale whats-new section for
> stable-updates
> Added tag(s) jessie.
It would be nice if information like this was available in the
document itself. As it is, the use of "&releasename" makes it hard
even to spot stale content.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Index: whats-new.dbk
===================================================================
--- whats-new.dbk (revision 9847)
+++ whats-new.dbk (working copy)
@@ -494,6 +494,32 @@
</section>
+<section id="stable-backports">
+ <title>The stable-backports section</title>
+ <para>
+ Note that this replaces the functionality previously provided by the
+ <ulink url="http://backports.debian.org/";>backports.debian.org archive</ulink>.
+ </para>
+ <para>
+ In order to use packages from <literal>&releasename;-backports</literal>,
+ you can add an entry to your <filename>sources.list</filename>:
+ </para>
+ <programlisting>deb &url-debian-mirror-eg;/debian &releasename;-backports main contrib
+deb-src &url-debian-mirror-eg;/debian &releasename;-backports 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>&releasename;-backports</literal> section and will consider them
+ when looking for packages to upgrade.
+ </para>
+ <para>
+ When a new package is made available via <literal>&releasename;-backports</literal>
+ to fix a security issue, this will be announced on the
+ <ulink url="http://lists.debian.org/debian-backports-announce/";>debian-backports-announce</ulink>
+ mailing list.
+ </para>
+</section>
+
<section id="stable-updates">
<title>The stable-updates section</title>
<para>
@@ -506,10 +532,6 @@
releases.
</para>
<para>
- Note that this replaces the functionality previously provided by the
- <ulink url="http://volatile.debian.org/";>volatile.debian.org archive</ulink>.
- </para>
- <para>
In order to use packages from <literal>&releasename;-updates</literal>,
you can add an entry to your <filename>sources.list</filename>:
</para>
@@ -529,32 +551,6 @@
</section>
-<section id="stable-backports">
- <title>The stable-backports section</title>
- <para>
- Note that this replaces the functionality previously provided by the
- <ulink url="http://backports.debian.org/";>backports.debian.org archive</ulink>.
- </para>
- <para>
- In order to use packages from <literal>&releasename;-backports</literal>,
- you can add an entry to your <filename>sources.list</filename>:
- </para>
- <programlisting>deb &url-debian-mirror-eg;/debian &releasename;-backports main contrib
-deb-src &url-debian-mirror-eg;/debian &releasename;-backports 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>&releasename;-backports</literal> section and will consider them
- when looking for packages to upgrade.
- </para>
- <para>
- When a new package is made available via <literal>&releasename;-backports</literal>
- to fix a security issue, this will be announced on the
- <ulink url="http://lists.debian.org/debian-backports-announce/";>debian-backports-announce</ulink>
- mailing list.
- </para>
-</section>
-
<section>
<title>GNOME 3</title>
