From a058a7af6a8e112ed81a13c1cbb6b0be02f8ea8e Mon Sep 17 00:00:00 2001
From: Joey Hess
Date: Fri, 26 Aug 2005 13:30:47 +0000
Subject: explain how to upload to secure-testing-master
git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@1653 e39458fd-73e7-0310-bf30-c45bca0a0e42
---
website/index.html | 44 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 44 insertions(+)
(limited to 'website/index.html')
diff --git a/website/index.html b/website/index.html
index 942f2b37cf..bb69c5b1b3 100644
--- a/website/index.html
+++ b/website/index.html
@@ -60,6 +60,50 @@
and may be checked out from
svn://svn.debian.org/secure-testing/.
+
+ Uploads to the secure-testing repository
+
+
+ To upload a package to the secure-testing repository, follow this
+ checklist:
+
+ - Only upload changes that have already been made in
+ unstable and are blocked by reaching testing by some other
+ issues. This is both to keep things in sync once the
+ new version from unstable reaches testing, and to avoid
+ breaking secure-testing too badly with fixes that have not
+ been tested first in unstable.
+ - Only make uploads for issues that the testing security
+ team plans to issue a DTSA announcement for.
+ - Use a version number that is less than the version
+ number of the fix in unstable, but greater than the version
+ number of the fix in testing. For example, if the fix is in
+ a new upstream version 1.0-1 in unstable, upload version
+ 1.0-0.1etch1 to secure-testing. If the fix is in version
+ 1.5-10 in unstable, use version 1.5-9etch1 in
+ secure-testing.
+ - Use "testing" as the distribution in the
+ changelog.
+ - Build the package in a testing chroot using pbuilder
+ so that all the dependencies are ok.
+ - Test the package.
+ - Upload to secure-testing-master.debian.net.
+ Here is a dput.cf snippet for that upload queue:
+
+ [secure-testing]
+ fqdn = secure-testing-master.debian.net
+ method = ftp
+ incoming = /pub/UploadQueue/
+ login = anonymous
+
+
+
+
+
+
+ Note that the above instructions are provisional until we get
+ everything set up.
+
Members and contacting the team
--
cgit v1.2.3