Package: developers-reference Version: 3.4.3 Severity: wishlist Tags: patch
Hi, While updating the French translation of the Developer's Reference (currently reviewed on debian-l10n-fre...@l.d.o), I noticed that part of the last paragraph about "NMUs and debian/changelog" might be obsolete. When Lenny was released, Marc 'HE' Brockschmid announced [0] that "the numbering scheme for Debian releases has been changed - point releases now use a true micro version number, so the first point release will be 5.0.1 instead of 5.0r1. The minor release number will be used for efforts such as lenny and a half." If this is still true, there is no more need to consider case "When the release number is not yet known (often the case for testing, at the beginning of release cycles)", since after Lenny (Debian 5.0) and Squeeze (Debian 6.0), the next testing (Squeeze+1) will be Debian 7.0. Please find attached the new.diff patch (usable after applying the update.diff I plan to upload in a week or so before uploading the French translation) more readable than the complete total.diff (usable on the current version of the Developer's Reference). [0] http://lists.debian.org/debian-devel-announce/2009/02/msg00003.html Cheers David
--- /mnt/donnees/1/debian/trans/dev-ref/pkgs.dbk 2010-05-23 15:15:33.615636320 -0400 +++ pkgs.dbk 2010-05-23 15:29:00.000000000 -0400 @@ -2050,17 +2050,12 @@ should be used, where <replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major and minor release numbers, and <replaceable>Z</replaceable> is a counter starting at <literal>1</literal>. -When the release number is not yet known (often the case for -<literal>testing</literal>, at the beginning of release cycles), the lowest -release number higher than the last stable release number must be used. For -example, while Etch (Debian 4.0) is stable, a security NMU to stable for a +While Lenny (Debian 5.0) is stable, a security NMU to stable for a package at version <literal>1.5-3</literal> would have version -<literal>1.5-3+deb40u1</literal>, whereas a security NMU to Lenny would get -version <literal>1.5-3+deb50u1</literal>. After the release of Lenny, security +<literal>1.5-3+deb50u1</literal>, whereas a security NMU to Squeeze would get +version <literal>1.5-3+deb60u1</literal>. After the release of Squeeze, security uploads to the <literal>testing</literal> distribution will be versioned -<literal>+deb51uZ</literal>, until it is known whether that release will be -Debian 5.1 or Debian 6.0 (if that becomes the case, uploads will be versioned -as <literal>+deb60uZ</literal>). +<literal>+deb70uZ</literal>. </para> </section>
--- /mnt/donnees/1/debian/trans/dev-ref/pkgs.dbk 2010-05-23 15:47:47.185179250 -0400 +++ pkgs.dbk 2010-05-23 15:45:36.000000000 -0400 @@ -2050,17 +2050,12 @@ should be used, where <replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major and minor release numbers, and <replaceable>Z</replaceable> is a counter starting at <literal>1</literal>. -When the release number is not yet known (often the case for -<literal>testing</literal>, at the beginning of release cycles), the lowest -release number higher than the last stable release number must be used. For -example, while Lenny (Debian 5.0) is stable, a security NMU to stable for a +While Lenny (Debian 5.0) is stable, a security NMU to stable for a package at version <literal>1.5-3</literal> would have version <literal>1.5-3+deb50u1</literal>, whereas a security NMU to Squeeze would get version <literal>1.5-3+deb60u1</literal>. After the release of Squeeze, security uploads to the <literal>testing</literal> distribution will be versioned -<literal>+deb61uZ</literal>, until it is known whether that release will be -Debian 6.1 or Debian 7.0 (if that becomes the case, uploads will be versioned -as <literal>+deb70uZ</literal>). +<literal>+deb70uZ</literal>. </para> </section>
--- pkgs.dbk 2010-05-23 15:42:50.000000000 -0400 +++ /mnt/donnees/1/debian/trans/dev-ref/pkgs.dbk 2010-05-23 15:38:51.101176259 -0400 @@ -2053,14 +2053,14 @@ When the release number is not yet known (often the case for <literal>testing</literal>, at the beginning of release cycles), the lowest release number higher than the last stable release number must be used. For -example, while Etch (Debian 4.0) is stable, a security NMU to stable for a +example, while Lenny (Debian 5.0) is stable, a security NMU to stable for a package at version <literal>1.5-3</literal> would have version -<literal>1.5-3+deb40u1</literal>, whereas a security NMU to Lenny would get -version <literal>1.5-3+deb50u1</literal>. After the release of Lenny, security +<literal>1.5-3+deb50u1</literal>, whereas a security NMU to Squeeze would get +version <literal>1.5-3+deb60u1</literal>. After the release of Lenny, security uploads to the <literal>testing</literal> distribution will be versioned -<literal>+deb51uZ</literal>, until it is known whether that release will be -Debian 5.1 or Debian 6.0 (if that becomes the case, uploads will be versioned -as <literal>+deb60uZ</literal>). +<literal>+deb61uZ</literal>, until it is known whether that release will be +Debian 6.1 or Debian 7.0 (if that becomes the case, uploads will be versioned +as <literal>+deb70uZ</literal>). </para> </section>
signature.asc
Description: OpenPGP digital signature
