Hi, A tiny nitpick: I found it jarring when the upgrading-checklist switched from past tense to present tense. I suppose it is because I kept finding myself switching context when reading it: unlike a changelog, which paraphrases a patch that will command the code to change, the upgrading checklist is directed to a packager that wants to know what has happened in the world.
How about something like this patch? It tries to give a little more detail about what changed in the style of a newscast while at it. Thanks for your hard work. upgrading-checklist.sgml | 24 +++++++++++++----------- 1 files changed, 13 insertions(+), 11 deletions(-) diff --git a/upgrading-checklist.sgml b/upgrading-checklist.sgml index e603852..80c778a 100644 --- a/upgrading-checklist.sgml +++ b/upgrading-checklist.sgml @@ -46,30 +46,32 @@ Unreleased. intended. </item> <tag>3.3</tag> - <item>Clarify the duties of a maintainer, require that the maintainer - address accept mail from Debian role accounts and the BTS, and require - at least one human with their personal email address + <item>Clarified the duties of a maintainer. The maintainer address + must accept mail from Debian role accounts and the BTS, and there + must be at least one human with their personal email address in <tt>Uploaders</tt> if the maintainer is a shared email address. </item> <tag>5.6.25</tag> - <item>Document the <tt>DM-Upload-Allowed</tt> field. + <item>Added a description of the <tt>DM-Upload-Allowed</tt> field + introduced by GR in 2007. </item> <tag>6.5</tag> - <item>Document the system state maintainer scripts can rely upon during + <item>Documented the system state maintainer scripts can rely upon during each possible invocation. 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>Better document the impact on system state when maintainer scripts - that are part of a circular dependency are run. Circular dependencies - are now a should not. + <item>Packages can rely on their dependencies being unpacked at + configure time, even if involved in a circular dependency. + Dependency loops involving a Pre-Depends will cause installation + to be aborted. Avoidable dependency loops are now a should not. </item> <tag>7.2</tag> - <item>Document the system state when <prgn>postinst</prgn> - and <prgn>prerm</prgn> scripts are run, and better document the special - case of dependency state for <prgn>postrm</prgn> + <item>Documented the system state when <prgn>postinst</prgn> + and <prgn>prerm</prgn> scripts are run, and clarified the special case + of dependency state for <prgn>postrm</prgn> scripts. <prgn>postrm</prgn> scripts are required to gracefully skip actions if their dependencies are not available. </item> -- 1.7.5.rc0 -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110406042634.GA16170@elie
