Policy: Stop recommending to serve HTML documents from /usr/share/doc.

[debian/debian-policy.git] / upgrading-checklist.sgml

diff --git a/upgrading-checklist.sgml b/upgrading-checklist.sgml
index c2d3c52f49bee7dd76dce1f8e8d898c390135efc..5714e841fdcd8e4e2d031619f24d7ffb72cbbc3c 100644 (file)
--- a/upgrading-checklist.sgml
+++ b/upgrading-checklist.sgml
@@ -34,6 +34,93 @@ picking your way through this list.
 
 <chapt> The checklist
 
 
 <chapt> The checklist
 

+<sect id="3.9.5.0"> Version 3.9.5.0
+<p>
+
+Unreleased.
+
+</p><p><taglist>
+<tag>5.4, 5.6.24</tag>
+  <item><tt>Checksums-Sha1</tt> and <tt>Checksums-Sha256</tt> are now
+  mandatory in <file>.dsc</file> files.
+  </item>
+<tag>5.6.25, 5.8.1</tag>
+  <item>The <tt>DM-Upload-Allowed</tt> field is obsolete.  Permissions
+  are now granted via <em>dak-commands</em> files.
+<tag>5.6.27</tag>
+  <item>New section documenting the <tt>Package-List</tt> field in Debian
+  source control files.
+  </item>
+<tag>5.6.28</tag>
+  <item>New section documenting the <tt>Package-Type</tt> field in source
+  package control files.
+  </item>
+<tag>11.5.2</tag>
+  <item>Stop recommending to serve HTML documents from
+  <file>/usr/share/doc/<var>package</var></file>.
+  </item>
+<tag>12.2</tag>
+  <item>Packages distributing Info documents should use
+  <package>install-info</package>'s trigger, and do not need anymore
+  to depend on <tt>dpkg (>= 1.15.4) | install-info</tt>.
+  </item>
+<tag>debconf</tag>
+  <item>The <tt>escape</tt> capability is now documented.
+  </item>
+</taglist></p>
+
+<sect id="3.9.4.0"> Version 3.9.4.0
+<p>
+
+Released August, 2012.
+
+</p><p><taglist>
+<tag>2.4</tag>
+  <item>New <em>tasks</em> archive section.
+  </item>
+<tag>4.9</tag>
+  <item><tt>build-arch</tt> and <tt>build-indep</tt> are now mandatory
+  targets in <file>debian/rules</file>.
+  </item>
+<tag>5.6.26</tag>
+  <item>New section documenting the <tt>Vcs-*</tt> fields, which are
+  already in widespread use.  Note the mechanism for specifying the Git
+  branch used for packaging in the Vcs-Git field.
+  </item>
+<tag>7.1</tag>
+  <item>The deprecated relations &lt; and &gt; now must not be used.
+  </item>
+<tag>7.8</tag>
+  <item>New <tt>Built-Using</tt> field, which must be used to document the
+  source packages for any binaries that are incorporated into this package
+  at build time.  This is used to ensure that the archive meets license
+  requirements for providing source for all binaries.
+  </item>
+<tag>8.6</tag>
+  <item>Policy for dependencies between shared libraries and other
+  packages has been largely rewritten to document the <tt>symbols</tt>
+  system and more clearly document handling of shared library ABI
+  changes.  <file>symbols</file> files are now recommended
+  over <file>shlibs</file> files in most situations.  All maintainers of
+  shared library packages should review the entirety of this section.
+  </item>
+<tag>9.1.1</tag>
+  <item>Packages must not assume the <file>/run</file> directory exists or
+  is usable without a dependency on <tt>initscripts (>= 2.88dsf-13.3)</tt>
+  until the stable release of Debian supports <file>/run</file>.
+  </item>
+<tag>9.7</tag>
+  <item>Packages including MIME configuration can now rely on triggers and
+  do not need to call update-mime.</item>
+<tag>9.11</tag>
+  <item>New section documenting general requirements for alternate init
+  systems and specific requirements for integrating with upstart.
+  </item>
+<tag>12.5</tag>
+  <item>All copyright files must be encoded in UTF-8.
+  </item>
+</taglist></p>
+

 <sect id="3.9.3.0"> Version 3.9.3.0
 <p>
 
 <sect id="3.9.3.0"> Version 3.9.3.0
 <p>
 


@@ -73,7 +160,7 @@ Released February, 2012.
   they will be ignored by cron.  They should replace those characters
   with <tt>_</tt>.  If a package provides multiple cron job files in the
   same directory, they should each start with the package name (possibly
   they will be ignored by cron.  They should replace those characters
   with <tt>_</tt>.  If a package provides multiple cron job files in the
   same directory, they should each start with the package name (possibly

-  modified as above), <tt>-</tt>, and then some suitable prefix.
+  modified as above), <tt>-</tt>, and then some suitable suffix.

   </item>
 <tag>9.10</tag>
   <item>Packages using doc-base do not need to call install-docs anymore.
   </item>
 <tag>9.10</tag>
   <item>Packages using doc-base do not need to call install-docs anymore.