+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>
+</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 < and > 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>
+
+Released February, 2012.
+
+</p><p><taglist>
+<tag>2.4</tag>
+ <item>New archive sections <em>education</em>, <em>introspection</em>,
+ and <em>metapackages</em> added.
+ </item>
+<tag>5.6.8</tag>
+ <item>The <tt>Architecture</tt> field in <file>*.dsc</file> files may
+ now contain the value <tt>any all</tt> for source packages building both
+ architecture-independent and architecture-dependent packages.
+ </item>
+<tag>7.1</tag>
+ <item>If a dependency is restricted to particular architectures, the
+ list of architectures must be non-empty.
+ </item>
+<tag>9.1.1</tag>
+ <item><file>/run</file> is allowed as an exception to the FHS and
+ replaces <file>/var/run</file>. <file>/run/lock</file>
+ replaces <file>/var/lock</file>. The FHS requirements for the older
+ directories apply to these directories as well. Backward compatibility
+ links will be maintained and packages need not switch to
+ referencing <file>/run</file> directly yet. Files in <file>/run</file>
+ should be stored in a temporary file system.
+ </item>
+<tag>9.1.4</tag>
+ <item>New section spelling out the requirements for packages that use
+ files in <file>/run</file>, <file>/var/run</file>,
+ or <file>/var/lock</file>. This generalizes information previously only
+ in 9.3.2.
+ </item>
+<tag>9.5</tag>
+ <item>Cron job file names must not contain <tt>.</tt> or <tt>+</tt> or
+ 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 suffix.
+ </item>
+<tag>9.10</tag>
+ <item>Packages using doc-base do not need to call install-docs anymore.
+ </item>
+<tag>10.7.4</tag>
+ <item>Packages that declare the same <tt>conffile</tt> may see left-over
+ configuration files from each other even if they conflict.
+ </item>
+<tag>11.8</tag>
+ <item>The Policy rules around Motif libraries were just a special case
+ of normal rules for non-free dependencies and were largely obsolete, so
+ they have been removed.
+ </item>
+<tag>12.5</tag>
+ <item><file>debian/copyright</file> is no longer required to list the
+ Debian maintainers involved in the creation of the package (although
+ note that the requirement to list copyright information is unchanged).
+ </item>
+<tag>copyright-format</tag>
+ <item>Version 1.0 of the "Machine-readable <file>debian/copyright</file>
+ file" specification is included.
+ </item>
+<tag>mime</tag>
+ <item>This separate document has been retired and and its (short)
+ contents merged into Policy section 9.7. There are no changes to the
+ requirements.
+ </item>
+<tag>perl</tag>
+ <item>Packages may declare an interest in the <var>perl-major-upgrade</var>
+ trigger to be notified of major upgrades of perl.
+ </item>
+<tag>virtual</tag>
+ <item><tt>ttf-japanese-{mincho, gothic}</tt> is renamed to
+ <tt>fonts-japanese-{mincho, gothic}</tt>.
+ </item>
+</taglist></p>
+
+<sect id="3.9.2.0"> Version 3.9.2.0
+<p>
+
+Released April, 2011.
+
+</p><p><taglist>
+<tag>*</tag>
+ <item>Multiple clarifications throughout Policy where "installed" was
+ used and the more precise terms "unpacked" or "configured" were
+ intended.
+ </item>
+<tag>3.3</tag>
+ <item>The maintainer address must accept mail from Debian role accounts
+ and the BTS. At least one human must be listed with their personal
+ email address in <tt>Uploaders</tt> if the maintainer is a shared email
+ address. The duties of a maintainer are also clearer.
+ </item>
+<tag>5</tag>
+ <item>All control fields are now classified as simple, folded, or
+ multiline, which governs whether their values must be a single line or
+ may be continued across multiple lines and whether line breaks are
+ significant.
+ </item>
+<tag>5.1</tag>
+ <item>Parsers are allowed to accept paragraph separation lines
+ containing whitespace, but control files should use completely empty
+ lines. Ordering of paragraphs is significant. Field names must be
+ composed of printable ASCII characters except colon and must not begin
+ with #.
+ </item>
+<tag>5.6.25</tag>
+ <item>The <tt>DM-Upload-Allowed</tt> field is now documented.
+ </item>
+<tag>6.5</tag>
+ <item>The system state maintainer scripts can rely upon during each
+ possible invocation is now documented. In several less-common cases,
+ this is stricter than Policy had previously documented. Packages with
+ complex maintainer scripts should be reviewed in light of this new
+ documentation.
+ </item>
+<tag>7.2</tag>
+ <item>The impact on system state when maintainer scripts that are part
+ of a circular dependency are run is now documented. Circular
+ dependencies are now a should not.
+ </item>
+<tag>7.2</tag>
+ <item>The system state when <prgn>postinst</prgn> and <prgn>prerm</prgn>
+ scripts are run is now documented, and the documentation of the special
+ case of dependency state for <prgn>postrm</prgn> scripts has been
+ improved. <prgn>postrm</prgn> scripts are required to gracefully skip
+ actions if their dependencies are not available.
+ </item>
+<tag>9.1.1</tag>
+ <item>GNU/Hurd systems are allowed <file>/hurd</file>
+ and <file>/servers</file> directories in the root filesystem.
+ </item>
+<tag>9.1.1</tag>
+ <item>Packages installing to architecture-specific subdirectories of
+ <file>/usr/lib</file> must use the value returned by
+ <prgn>dpkg-architecture -qDEB_HOST_MULTIARCH</prgn>, not by
+ <prgn>dpkg-architecture -qDEB_HOST_GNU_TYPE</prgn>; this is a path change
+ on i386 architectures and a no-op for other architectures.
+ </item>
+<tag>virtual</tag>
+ <item><tt>mailx</tt> is now a virtual package provided by packages that
+ install <prgn>/usr/bin/mailx</prgn> and implement at least the
+ POSIX-required interface.
+ </item>
+</taglist></p>
+
+<sect id="3.9.1.0"> Version 3.9.1.0
+<p>
+
+Released July, 2010.