[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[developers-reference] 01/01: Update the section about the package tracker

This is an automated email from the git hooks/post-receive script.

hertzog pushed a commit to branch master
in repository developers-reference.

commit 66dcf83329873f0c531fbdb7fe88329d0e303721
Author: Raphaël Hertzog <hertzog@debian.org>
Date:   Wed Dec 9 10:46:34 2015 +0100

    Update the section about the package tracker
    
    Document tracker.debian.org instead of packages.qa.debian.org.
---
 beyond-pkging.dbk |   6 +-
 common.ent        |   1 +
 debian/changelog  |   8 ++
 pkgs.dbk          |   4 +-
 resources.dbk     | 330 ++++++++++++------------------------------------------
 5 files changed, 84 insertions(+), 265 deletions(-)

diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk
index 25987fe..7963b49 100644
--- a/beyond-pkging.dbk
+++ b/beyond-pkging.dbk
@@ -204,7 +204,7 @@ or a binary package.
 </para>
 <para>
 You may also be interested in contacting the persons who are subscribed to a
-given source package via <xref linkend="pkg-tracking-system"/>.  You can do so
+given source package via <xref linkend="pkg-tracker"/>.  You can do so
 by using the <literal><replaceable>package</replaceable>@&pts-host;</literal> email
 address.
 </para>
@@ -475,7 +475,7 @@ If the audit did not reveal any problem, you can build the package and
 upload it to Debian. Remember that even if you're not the maintainer,
 as a sponsor you are still responsible for what you upload to Debian. That's
 why you're encouraged to keep up with the package through the
-<xref linkend="pkg-tracking-system"/>.
+<xref linkend="pkg-tracker"/>.
 </para>
 <para>
 Note that you should not need to modify the source package to put your name
@@ -535,7 +535,7 @@ etc.).
 </para>
 <para>
 You might want to check out the Package Tracking System (see <xref
-linkend="pkg-tracking-system"/>) to verify if the
+linkend="pkg-tracker"/>) to verify if the
 maintainer has not missed something important. Maybe there are translations
 updates sitting in the BTS that could have been integrated. Maybe the package
 has been NMUed and the maintainer forgot to integrate the changes from the
diff --git a/common.ent b/common.ent
index a1ec2b0..2bf5322 100644
--- a/common.ent
+++ b/common.ent
@@ -47,6 +47,7 @@
 <!ENTITY packages-host "packages.debian.org">
 <!ENTITY bugs-host "bugs.debian.org">
 <!ENTITY pts-host "packages.qa.debian.org">
+<!ENTITY tracker-host "tracker.debian.org">
 <!ENTITY ftp-master-host "ftp-master.debian.org">
 <!ENTITY ftp-upload-host "ftp.upload.debian.org">
 <!ENTITY ftp-eu-upload-host "ftp.eu.upload.debian.org">
diff --git a/debian/changelog b/debian/changelog
index 57df7cf..010de91 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+developers-reference (3.4.17) unstable; urgency=medium
+
+  * Team upload.
+  * Update the section about the package tracker to document
+    tracker.debian.org instead of packages.qa.debian.org.
+
+ -- Raphaël Hertzog <hertzog@debian.org>  Wed, 09 Dec 2015 10:44:56 +0100
+
 developers-reference (3.4.16) unstable; urgency=medium
 
   [ Charles Plessy ]
diff --git a/pkgs.dbk b/pkgs.dbk
index d4acfad..bbac343 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -1479,7 +1479,7 @@ package's official maintainer in the bug system.  This will happen
 automatically once you upload a new version with an updated
 <literal>Maintainer</literal> field, although it can take a few hours after
 the upload is done.  If you do not expect to upload a new version for a while,
-you can use <xref linkend="pkg-tracking-system"/> to get the bug reports.
+you can use <xref linkend="pkg-tracker"/> to get the bug reports.
 However, make sure that the old maintainer has no problem with the fact that
 they will continue to receive the bugs during that time.
 </para>
@@ -2356,7 +2356,7 @@ Uploaders: John Buzz &lt;jbuzz@debian.org&gt;, Adam Rex &lt;arex@debian.org&gt;
 </listitem>
 <listitem>
 <para>
-Using the PTS (<xref linkend="pkg-tracking-system"/>), the co-maintainers
+Using the PTS (<xref linkend="pkg-tracker"/>), the co-maintainers
 should subscribe themselves to the appropriate source package.
 </para>
 </listitem>
diff --git a/resources.dbk b/resources.dbk
index 5bbcfcd..609ca03 100644
--- a/resources.dbk
+++ b/resources.dbk
@@ -999,16 +999,18 @@ of the package has been recompiled on all architectures.
 
 </section>
 
-<section id="pkg-tracking-system">
-<title>The Package Tracking System</title>
+<section id="pkg-tracker">
+<title>The Debian Package Tracker</title>
 <para>
-The Package Tracking System (PTS) is an email-based tool to track the activity
-of a source package.  This really means that you can get the same emails that
-the package maintainer gets, simply by subscribing to the package in the PTS.
+The Debian Package Tracker is an email and web-based tool to track the activity
+of a source package. You can get the same emails that
+the package maintainer gets, simply by subscribing to the package in the Debian
+Package Tracker.
 </para>
 <para>
-Each email sent through the PTS is classified under one of the keywords listed
-below.  This will let you select the mails that you want to receive.
+Each email sent through the package tracker is classified under one of the
+keywords listed below.  This will let you select the mails that you want
+to receive.
 </para>
 <para>
 By default you will get:
@@ -1041,16 +1043,17 @@ package is accepted.
 </listitem>
 </varlistentry>
 <varlistentry>
-<term><literal>katie-other</literal></term>
+<term><literal>archive</literal></term>
 <listitem>
 <para>
 Other warning and error emails from <command>dak</command> (such as an
-override disparity for the section and/or the priority field).
+override disparity for the section and/or the priority field). Also includes
+notifications of package removals.
 </para>
 </listitem>
 </varlistentry>
 <varlistentry>
-<term><literal>buildd</literal></term>
+<term><literal>build</literal></term>
 <listitem>
 <para>
 Build failures notifications sent by the network of build daemons, they contain
@@ -1062,11 +1065,11 @@ a pointer to the build logs for analysis.
 <term><literal>default</literal></term>
 <listitem>
 <para>
-Any non-automatic email sent to the PTS by people who wanted to contact the
-subscribers of the package.  This can be done by sending mail to
-<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>.
-In order to prevent spam, all messages sent to these addresses must contain the
-<literal>X-PTS-Approved</literal> header with a non-empty value.
+Any non-recognized email sent to the package tracker through
+<literal>dispatch+<replaceable>sourcepackage</replaceable>@&tracker-host;</literal>.
+In order to prevent spam, all messages sent to these addresses must
+contain the <literal>X-Distro-Tracker-Approved</literal> header with a
+non-empty value.
 </para>
 </listitem>
 </varlistentry>
@@ -1084,10 +1087,9 @@ aliases.
 <listitem>
 <para>
 Regular summary emails about the package's status, including progression
-into <literal>testing</literal>,
-<ulink url="&url-dehs;">DEHS</ulink> notifications of
-new upstream versions, and a notification if the package is removed or
-orphaned.
+into <literal>testing</literal>. Ideally it should also include
+notifications of new upstream versions, and a notification if the package
+is orphaned (but this is not yet the case).
 </para>
 </listitem>
 </varlistentry>
@@ -1100,7 +1102,7 @@ You can also decide to receive additional information:
 <term><literal>upload-binary</literal></term>
 <listitem>
 <para>
-The email notification from <command>katie</command> when an uploaded binary
+The email notification from <command>dak</command> when an uploaded binary
 package is accepted.  In other words, whenever a build daemon or a porter
 uploads your package for another architecture, you can get an email to track
 how your package gets recompiled for all architectures.
@@ -1108,18 +1110,17 @@ how your package gets recompiled for all architectures.
 </listitem>
 </varlistentry>
 <varlistentry>
-<term><literal>cvs</literal></term>
+<term><literal>vcs</literal></term>
 <listitem>
 <para>
 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.
+maintainer has set up forwarding of commit notifications to the package
+tracker.
 </para>
 </listitem>
 </varlistentry>
 <varlistentry>
-<term><literal>ddtp</literal></term>
+<term><literal>translation</literal></term>
 <listitem>
 <para>
 Translations of descriptions or debconf templates submitted to the Debian
@@ -1145,11 +1146,11 @@ Bugs reports and comments from derivative distributions (for example Ubuntu).
 </listitem>
 </varlistentry>
 </variablelist>
-<section id="pts-commands">
-<title>The PTS email interface</title>
+<section id="pkg-tracker-commands">
+<title>The package tracker email interface</title>
 <para>
-You can control your subscription(s) to the PTS by sending various commands to
-<email>pts@qa.debian.org</email>.
+You can control your subscription(s) to the package tracker by sending
+various commands to <email>control@tracker.debian.org</email>.
 </para>
 <variablelist>
 <varlistentry>
@@ -1160,8 +1161,8 @@ Subscribes <replaceable>email</replaceable> to communications related to the
 source package <replaceable>sourcepackage</replaceable>.  Sender address is
 used if the second argument is not present.  If
 <replaceable>sourcepackage</replaceable> is not a valid source package, you'll
-get a warning.  However if it's a valid binary package, the PTS will subscribe
-you to the corresponding source package.
+get a warning.  However if it's a valid binary package, the package
+tracker will subscribe you to the corresponding source package.
 </para>
 </listitem>
 </varlistentry>
@@ -1198,85 +1199,9 @@ specified.
 <listitem>
 <para>
 Tells you the keywords that you are accepting.  For an explanation of keywords,
-<link linkend="pkg-tracking-system">see above</link>.  Here's a quick
-summary:
-</para>
-<itemizedlist>
-<listitem>
-<para>
-<literal>bts</literal>: mails coming from the Debian Bug Tracking System
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>bts-control</literal>: reply to mails sent to
-&email-bts-control;
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>summary</literal>: automatic summary mails about the state of a
-package
-</para>
-</listitem>
-<listitem>
-<para>
-<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>
-<para>
-<literal>ddtp</literal>: translations of descriptions and debconf templates
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>derivatives</literal>: changes made on the package by derivative
-distributions
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>derivatives-bugs</literal>: bugs reports and comments from derivative
-distributions
+<link linkend="pkg-tracker">see above</link>.
 </para>
 </listitem>
-<listitem>
-<para>
-<literal>upload-source</literal>: announce of a new source upload that has been
-accepted
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>upload-binary</literal>: announce of a new binary-only upload
-(porting)
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>katie-other</literal>: other mails from ftpmasters (override
-disparity, etc.)
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>buildd</literal>: build failures notifications from build daemons
-</para>
-</listitem>
-<listitem>
-<para>
-<literal>default</literal>: all the other mails (those which aren't automatic)
-</para>
-</listitem>
-</itemizedlist>
-</listitem>
 </varlistentry>
 <varlistentry>
 <term><literal>keyword &lt;sourcepackage&gt; [&lt;email&gt;]</literal></term>
@@ -1333,44 +1258,50 @@ upload.
 </para>
 </section>
 
-<section id="pts-mail-filtering">
-<title>Filtering PTS mails</title>
+<section id="pkg-tracker-mail-filtering">
+<title>Filtering mails from the package tracker</title>
 <para>
-Once you are subscribed to a package, you will get the mails sent to
-<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>.
-Those mails have special headers appended to let you filter them in a special
-mailbox (e.g.  with <command>procmail</command>).  The added headers are
-<literal>X-Loop</literal>, <literal>X-PTS-Package</literal>,
-<literal>X-PTS-Keyword</literal> and <literal>X-Unsubscribe</literal>.
+Once you are subscribed to a package, you will get mails forwarded by
+the package tracker. Those mails have special headers appended to let you
+filter them in a special mailbox (e.g.  with <command>procmail</command>).
+The added headers are
+<literal>X-Loop</literal>, <literal>X-Distro-Tracker-Package</literal>,
+<literal>X-Distro-Tracker-Keyword</literal>, <literal>X-Debian-Package</literal>,
+<literal>X-Debian</literal> and <literal>List-Unsubscribe</literal>.
 </para>
 <para>
 Here is an example of added headers for a source upload notification on the
 <systemitem role="package">dpkg</systemitem> package:
 </para>
 <screen>
-X-Loop: dpkg@&pts-host;
-X-PTS-Package: dpkg
-X-PTS-Keyword: upload-source
-List-Unsubscribe: &lt;mailto:pts@qa.debian.org?body=unsubscribe+dpkg&gt;
+X-Loop: dispatch@&tracker-host;
+X-Distro-Tracker-Package: dpkg
+X-Distro-Tracker-Keyword: upload-source
+X-Debian-Package: dpkg
+X-Debian: tracker.debian.org
+List-Unsubscribe: &lt;mailto:control@tracker.debian.org?body=unsubscribe%20dpkg&gt;
 </screen>
 </section>
 
-<section id="pts-vcs-commit">
-<title>Forwarding VCS commits in the PTS</title>
+<section id="pkg-tracker-vcs-commit">
+<title>Forwarding VCS commits to the package tracker</title>
 <para>
 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
+package, you may want to forward the commit notification to the package tracker
+so that the subscribers (and possible co-maintainers) can closely follow the package's
 evolution.
 </para>
 <para>
 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 <literal>cvs</literal> keyword will receive
-these notifications. Note that the mail needs to be sent from a
-<literal>debian.org</literal> machine, otherwise you'll have to add
-the <literal>X-PTS-Approved: 1</literal> header.
+have to make sure it sends a copy of those mails to the package tracker at
+<literal>dispatch@&tracker-host;</literal> or at
+<literal>dispatch+<replaceable>sourcepackage</replaceable>_vcs@&tracker-host;</literal>.
+In the former case, you must make sure that the package tracker is able to identify
+the source package and the appropriate keyword... either by adding the headers 
+<literal>X-Distro-Tracker-Package: <replaceable>sourcepackage</replaceable></literal> and
+<literal>X-Distro-Tracker-Keyword: vcs</literal> or by relying on the
+fact that the package tracker will detect the <literal>X-Git-Repo</literal> header
+and assume that the name of the git repository matches a source package.
 </para>
 <para>
 For Subversion repositories, the usage of svnmailer is recommended.
@@ -1379,147 +1310,26 @@ See <ulink url="&url-alioth-pkg;" /> for an example on how to do it.
 </section>
 
 <section id="pts-web">
-<title>The PTS web interface</title>
+<title>The package tracker web interface</title>
 <para>
-The PTS has a web interface at <ulink
-url="https://&pts-host;/";></ulink> that puts together a lot of
+The package tracker has a web interface at <ulink
+url="https://&tracker-host;/";></ulink> that puts together a lot of
 information about each source package.  It features many useful links (BTS, QA
 stats, contact information, DDTP translation status, buildd logs) and gathers
 much more information from various places (30 latest changelog entries, testing
 status, etc.).  It's a very useful tool if you want to know what's going on with
-a specific source package.  Furthermore there's a form that allows easy
-subscription to the PTS via email.
+a specific source package.  Furthermore, once authenticated, you can subscribe
+and unsubscribe from any package with a single click.
 </para>
 <para>
 You can jump directly to the web page concerning a specific source package with
 a URL like
-<literal>https://&pts-host;/<replaceable>sourcepackage</replaceable></literal>.
-</para>
-<para>
-This web interface has been designed like a portal for the development of
-packages: you can add custom content on your packages' pages.  You can add
-static information (news items that are meant to stay available indefinitely)
-and news items in the latest news section.
+<literal>https://&tracker-host;/pkg/<replaceable>sourcepackage</replaceable></literal>.
 </para>
 <para>
-Static news items can be used to indicate:
-</para>
-<itemizedlist>
-<listitem>
-<para>
-the availability of a project hosted on
-<link linkend="alioth">Alioth</link> for co-maintaining the package
-</para>
-</listitem>
-<listitem>
-<para>
-a link to the upstream web site
-</para>
-</listitem>
-<listitem>
-<para>
-a link to the upstream bug tracker
-</para>
-</listitem>
-<listitem>
-<para>
-the existence of an IRC channel dedicated to the software
-</para>
-</listitem>
-<listitem>
-<para>
-any other available resource that could be useful in the maintenance of the
-package
-</para>
-</listitem>
-</itemizedlist>
-<para>
-Usual news items may be used to announce that:
-</para>
-<itemizedlist>
-<listitem>
-<para>
-beta packages are available for testing
-</para>
-</listitem>
-<listitem>
-<para>
-final packages are expected for next week
-</para>
-</listitem>
-<listitem>
-<para>
-the packaging is about to be redone from scratch
-</para>
-</listitem>
-<listitem>
-<para>
-backports are available
-</para>
-</listitem>
-<listitem>
-<para>
-the maintainer is on vacation (if they wish to publish this information)
-</para>
-</listitem>
-<listitem>
-<para>
-a NMU is being worked on
-</para>
-</listitem>
-<listitem>
-<para>
-something important will affect the package
-</para>
-</listitem>
-</itemizedlist>
-<para>
-Both kinds of news are generated in a similar manner: you just have to send an
-email either to <email>pts-static-news@qa.debian.org</email> or to
-<email>pts-news@qa.debian.org</email>.  The mail should indicate which package
-is concerned by having the name of the source package in a
-<literal>X-PTS-Package</literal> mail header or in a <literal>Package</literal>
-pseudo-header (like the BTS reports).  If a URL is available in the
-<literal>X-PTS-Url</literal> mail header or in the <literal>Url</literal>
-pseudo-header, then the result is a link to that URL instead of a complete news
-item.
-</para>
-<para>
-Here are a few examples of valid mails used to generate news items in the PTS.
-The first one adds a link to the viewsvn interface of debian-cd in the Static
-information section:
-</para>
-<screen>
-From: Raphael Hertzog &lt;hertzog@debian.org&gt;
-To: pts-static-news@qa.debian.org
-Subject: Browse debian-cd SVN repository
-
-Package: debian-cd
-Url: http://svn.debian.org/viewsvn/debian-cd/trunk/
-</screen>
-<para>
-The second one is an announcement sent to a mailing list which is also sent to
-the PTS so that it is published on the PTS web page of the package.  Note the
-use of the BCC field to avoid answers sent to the PTS by mistake.
-</para>
-<screen>
-From: Raphael Hertzog &lt;hertzog@debian.org&gt;
-To: debian-gtk-gnome@&lists-host;
-Bcc: pts-news@qa.debian.org
-Subject: Galeon 2.0 backported for woody
-X-PTS-Package: galeon
-
-Hello gnomers!
-
-I'm glad to announce that galeon has been backported for woody. You'll find
-everything here:
-...
-</screen>
-<para>
-Think twice before adding a news item to the PTS because you won't be able to
-remove it later and you won't be able to edit it either.  The only thing that
-you can do is send a second news item that will deprecate the information
-contained in the previous one.
+The web interface is easy to extend and you are welcome to integrate more
+useful data in it. If you want to contribute, have a look at
+<ulink url="https://&tracker-host;/docs/contributing.html";></ulink>.
 </para>
 </section>
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/collab-maint/developers-reference.git
Reply to: