From 762a28817b9e2f351cb3f03a089632e3beb832eb Mon Sep 17 00:00:00 2001
From: hertzog <hertzog@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Mon, 25 Feb 2008 20:21:33 +0000
Subject: [PATCH] * Update information concerning the Package Tracking System.

git-svn-id: svn://anonscm.debian.org/ddp/developers-reference/trunk@4941 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 debian/changelog |  1 +
 resources.dbk    | 41 ++++++++++++++++++++++++++++++++---------
 2 files changed, 33 insertions(+), 9 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 79d4911..38d2e34 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -37,6 +37,7 @@ developers-reference (3.3.9) unstable; urgency=low
     a reference to #debian-dpkg instead.
   * Remove all stuff concerning non-US.
   * Update information concerning Alioth.
+  * Update information concerning the Package Tracking System.
 
  -- Andreas Barth <aba@not.so.argh.org>  Sat, 16 Jun 2007 11:41:41 -0600
 
diff --git a/resources.dbk b/resources.dbk
index 6c9deb7..c259068 100644
--- a/resources.dbk
+++ b/resources.dbk
@@ -1057,6 +1057,15 @@ In order to prevent spam, all messages sent to these addresses must contain the
 </listitem>
 </varlistentry>
 <varlistentry>
+<term><literal>contact</literal></term>
+<listitem>
+<para>
+Mails sent to the maintainer through the *@packages.debian.org email
+aliases.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
 <term><literal>summary</literal></term>
 <listitem>
 <para>
@@ -1085,8 +1094,10 @@ how your package gets recompiled for all architectures.
 <term><literal>cvs</literal></term>
 <listitem>
 <para>
-CVS commit notifications, if the package has a CVS repository and the
-maintainer has set up forwarding commit notifications to the PTS.
+VCS commit notifications, if the package has a VCS repository and the
+maintainer has set up forwarding of commit notifications to the PTS. The
+"cvs" name is historic, in most cases commit notifications will come
+from some other VCS like subversion or git.
 </para>
 </listitem>
 </varlistentry>
@@ -1185,7 +1196,13 @@ package
 </listitem>
 <listitem>
 <para>
-<literal>cvs</literal>: notification of CVS commits
+<literal>contact</literal>: mails sent to the maintainer through the
+*@packages.debian.org aliases
+</para>
+</listitem>
+<listitem>
+<para>
+<literal>cvs</literal>: notification of VCS commits
 </para>
 </listitem>
 <listitem>
@@ -1298,24 +1315,30 @@ Here is an example of added headers for a source upload notification on the
 X-Loop: dpkg@&pts-host;
 X-PTS-Package: dpkg
 X-PTS-Keyword: upload-source
-X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org
+List-Unsubscribe: &lt;mailto:pts@qa.debian.org?body=unsubscribe+dpkg&gt;
 </screen>
 </section>
 
-<section id="pts-cvs-commit">
-<title>Forwarding CVS commits in the PTS</title>
+<section id="pts-vcs-commit">
+<title>Forwarding VCS commits in the PTS</title>
 <para>
-If you use a publicly accessible CVS repository for maintaining your Debian
+If you use a publicly accessible VCS repository for maintaining your Debian
 package, you may want to forward the commit notification to the PTS so that the
 subscribers (and possible co-maintainers) can closely follow the package's
 evolution.
 </para>
 <para>
-Once you set up the CVS repository to generate commit notifications, you just
+Once you set up the VCS repository to generate commit notifications, you just
 have to make sure it sends a copy of those mails to
 <literal><replaceable>sourcepackage</replaceable>_cvs@&pts-host;</literal>.
 Only the people who accept the <emphasis>cvs</emphasis> keyword will receive
-these notifications.
+these notifications. Note that the mail need to be sent from a
+<literal>debian.org</literal> machine, otherwise you'll have to add
+the <literal>X-PTS-Approved: 1</literal> header.
+</para>
+<para>
+For Subversion repositories, the usage of svnmailer is recommended.
+See <ulink url="&url-alioth-pkg;" /> for an example on how to do it.
 </para>
 </section>
 
-- 
2.30.2