From: he Date: Sat, 7 Jun 2008 10:47:12 +0000 (+0000) Subject: Update the instructions for uploads to the (old)stable X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=commitdiff_plain;h=0adcfcc1b39c4d51e7131f1157a3919ab367565b Update the instructions for uploads to the (old)stable distributions. Emphasize the importance of contacting the SRM team before upload. Closes: #459343 git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@5219 313b444b-1b9f-4f58-a734-7bb04f332e8d --- diff --git a/debian/changelog b/debian/changelog index a3e0224..305102e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -27,6 +27,9 @@ developers-reference (3.4.0) UNRELEASED; urgency=low the dev-ref up to the state of porting in the year 2008. Also fixes several wording issues, such as possible misunderstandings about the need to rebuild uploads. Closes: #483226 + * Update the instructions for uploads to the (old)stable + distributions. Emphasize the importance of contacting the SRM + team before upload. Closes: #459343 -- Marc 'HE' Brockschmidt Sun, 01 Jun 2008 16:26:33 +0200 diff --git a/pkgs.dbk b/pkgs.dbk index db52c3d..3a2813b 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -284,16 +284,25 @@ It is not possible to upload a package into several distributions at the same time.
-Special case: uploads to the <literal>stable</literal> distribution +Special case: uploads to the <literal>stable</literal> and +<literal>oldstable</literal> distributions Uploading to stable means that the package will transfered -to the proposed-updates-new-queue for review by the stable +to the proposed-updates-new queue for review by the stable release managers, and if approved will be installed in stable-proposed-updates directory of the Debian archive. From there, it will be included in stable with the next point release. +To ensure that your upload will be accepted, you should discuss the changes +with the stable release team before you upload. For that, send a mail to +the &email-debian-release; mailing list, including the patch you want to +apply to the package version currently in stable. Always +be verbose and detailed in your changelog entries for uploads to the +stable distribution. + + Extra care should be taken when uploading to stable. Basically, a package should only be uploaded to stable if one of the following happens: @@ -321,7 +330,10 @@ security problems as well. However, this practice is deprecated, as uploads used for Debian security advisories are automatically copied to the appropriate proposed-updates archive when the advisory is released. See for detailed information on handling -security problems. +security problems. If the security teams deems the problem to be too +benign to be fixed through a DSA, the stable release +managers are usually willing to include your fix nonetheless in a regular +upload to stable. Changing anything else in the package that isn't important is discouraged, @@ -338,19 +350,9 @@ rejected. Making changes to dependencies of other packages (by messing with making those other packages uninstallable, is strongly discouraged. -The Release Team (which can be reached at -&email-debian-release;) will regularly evaluate the uploads to -stable-proposed-updates and decide if your package can be -included in stable. Please be clear (and verbose, if -necessary) in your changelog entries for uploads to -stable, because otherwise the package won't be considered -for inclusion. - - -It's best practice to speak with the stable release manager -before uploading to -stable/stable-proposed-updates, so -that the uploaded package fits the needs of the next point release. +Uploads to the oldstable distributions are possible as +long as it hasn't been archived. The same rules as for stable + apply.