From 04add2a35a1a9a3aec21a20e0cadd677d59dd245 Mon Sep 17 00:00:00 2001 From: Stefan Fritsch Date: Sat, 6 Oct 2007 18:38:06 +0000 Subject: more website changes git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@6836 e39458fd-73e7-0310-bf30-c45bca0a0e42 --- website/helping.html | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++ website/index.html | 11 +++++++++- website/style.css | 6 +++--- website/uploading.html | 17 +++++++++++++--- 4 files changed, 82 insertions(+), 7 deletions(-) create mode 100644 website/helping.html (limited to 'website') diff --git a/website/helping.html b/website/helping.html new file mode 100644 index 0000000000..4e615393d6 --- /dev/null +++ b/website/helping.html @@ -0,0 +1,55 @@ + + + Helping testing security + + + + +
+ + + + + Debian Project +
+
+ + + + + + + + + + + +
+ Debian testing security team +
+ + +
+ +

As non-Debian Developer

+ +

As Debian package maintainer

+ +

As Debian Developer

+ + + + +

$Id: index.html 6493 2007-09-04 11:06:04Z nion $

+ + Valid HTML 4.01! + + Valid CSS! + + + diff --git a/website/index.html b/website/index.html index c57de80b1d..d5a08ba756 100644 --- a/website/index.html +++ b/website/index.html @@ -129,7 +129,7 @@ +

Internal information

+ +

$Id$

diff --git a/website/style.css b/website/style.css index ec13c9e885..6458b55581 100644 --- a/website/style.css +++ b/website/style.css @@ -114,17 +114,17 @@ td { a:link { color: #0000FF; - text-decoration: none; + text-decoration: underline; } a:visited { color: #800080; - text-decoration: none; + text-decoration: underline; } a:active { color: #FF0000; - text-decoration: none; + text-decoration: underline; } a:hover{ diff --git a/website/uploading.html b/website/uploading.html index 41cf304955..73f281950c 100644 --- a/website/uploading.html +++ b/website/uploading.html @@ -39,16 +39,19 @@ To upload a package to the secure-testing repository, any Debian developer may follow this checklist:
    +
  1. Contact the team first to avoid duplicate work.
    2. +
  2. 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.
    3. +
  3. If the orig.tar.gz is already on security.debian.org (either in stable-security or in testing-security) don't include it in the upload. If in doubt, ask the team.
    4. -
  4. Contact the team first to avoid duplicate work.
    5. +
  5. 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 (including a possible +b1 for binNMUs). @@ -56,18 +59,22 @@ upload version 1.0-1~lenny1 to testing-security. If the current version in testing is 1.2-3 and the fix is backported to this version, upload version 1.2-3+lenny1 to testing-security.
    6. +
  6. Use "testing-security" as the distribution in the changelog.
    7. +
  7. Build the package in a testing chroot using pbuilder so that all the dependencies are ok. Be sure to build with the -sa switch to include source, unless the source is - already in the testing-security archive. -
    8. + already in the testing-security archive. +
  8. Test the package. Diff the package against the version in testing (if backporting fixes). Use debdiff on both source and binary packages.
    9. +
  9. Sign the package. Any Debian developer in the keyring can do so.
    10. +
  10. Upload to security-master.debian.org. Here is a dput.cf snippet for that upload queue: 
    @@ -82,6 +89,10 @@
+

Information about releasing the packages can be found in the + howto-DTSA + file in the SVN repository. +

$Id: index.html 6493 2007-09-04 11:06:04Z nion $

-- cgit v1.2.3