Differences between revisions 1 and 31 (spanning 30 versions)
Revision 1 as of 2005-09-11 08:58:34
Size: 3380
Comment:
Revision 31 as of 2014-02-21 09:17:03
Size: 4326
Comment: update link to PTS replacement
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format wiki
Line 4: Line 3:
== Developer information concerning the Package Tracking System == = Package Tracking System (PTS) =

== Introduction ==
The Package Tracking System lets you follow almost everything related to the life of a package. It's of interest for co-maintainers, advanced users, QA members, ...

The PTS is actually a website :
 http://packages.qa.debian.org

You can access information known by the PTS also via a (work in progress) '''[[/SoapInterface|SOAP interface]]''', or the '''[[/RdfInterface|Linked Data interface]]'''.

== Contributing to the Package Tracking System ==
Line 8: Line 17:
$ export CVSROOT=:pserver:anonymous@cvs.debian.org:/cvs/qa
$ cvs login
$ cvs co pts
$ svn co svn://svn.debian.org/qa/trunk/pts
Line 12: Line 19:
(you can use :ext:<yourdebianlogin>@cvs.debian.org:/cvs/qa if you're a Debian developer in the "qa" group and you'll have write access to it) (you can use svn+ssh://<yourdebianlogin>@svn.debian.org/svn/qa/trunk/pts if you're a Debian developer in the "qa" group and you'll have write access to it)

You can also browse the sources at : http://anonscm.debian.org/viewvc/qa/trunk/pts/
Line 16: Line 25:
Raphael Hertzog gave a short overview of the PTS intended for developers. Please [http://www.ouaza.com/textes/conf/pts-internals.pdf check the slides]. Raphael Hertzog gave a short overview of the PTS intended for developers. Please [[http://ouaza.com/static/conf/pts-internals.pdf|check the slides]]. Some of the information is outdated (for example VERP has been implemented together with a bounce handler) but the basic structure of the software is unchanged.
Line 20: Line 29:
'''VERP bounce handling''' '''Fix bugs and implement wishlist from the BTS'''
Line 22: Line 31:
For the moment, bounces from the PTS are sent to owner@p.q.d.o (buxy) and they're treated manually. We need to add an automatic bounce handler. But it needs to be a bit smart: don't remove someone on the first bounce, but wait until *all* the mails sent during 3 different days to a given address bounces. http://bugs.debian.org/qa.debian.org (those with the "pts" usertag of course : see also: http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=pts&user=qa.debian.org%40packages.debian.org )
Line 24: Line 33:
 1. Add VERP Mail From header in bin/dispatch.pl (see this patch).
 1. Create a new script dedicated to the bounce handling.
'''Provide RSS feeds for each source package'''

All the news should be available as an RSS feed. But the RSS feed should be richer: it should integrate more stuff like the upload of a new Ubuntu version with the corresponding Debian patch and also entries for the problems displayed. The difficulty is to have a good date for the various entries that are not tied to an email.

'''Subscribe to set of packages'''

The members of the Gnome team would like to subscribe with a single command to all Gnome-related packages. The idea is to add a new "group subscription" feature. The GNOME team maintain the list of packages and anyone can then "groupsubscribe gnome-desktop" and be automatically subscribed to all relevant packages.

This feature could then be used by little "bugsquad team" to quickly move from one package to another.

'''Possibility to reset keywords to the default state'''

Right now, once you set some specific keywords on a given source package, you will always have a customized list keyword for this source package. And in some cases, you don't want anymore. A "keywordreset" command would be welcome.

Also te keyword DB is cluttered with wrong email/source package. It should be periodically cleaned of subscriptions which don't exist anymore.
Line 35: Line 57:
Each maintainer has the possibility to send (static and usual) news to the PTS. However he can't remove news which are outdated. Because of this, the maintainer are not using this very important feature. This needs to change ! Each maintainer has the possibility to send (static and usual) news to the PTS. However he can't remove news which are outdated. Because of this, the maintainer is not using this very important feature. This needs to change!
Line 37: Line 59:
'''Integrate better with <package>@packages.debian.org''' '''Integrate debtags information'''
Line 39: Line 61:
The main maintainer can be contacted at <srcpackage>@packages.debian.org and co-maintainers can be contacted at <srcpackage>@packages.qa.debian.org. We should integrate both more tightely so that
we can easily reach all contributors to a single package.
Debtags is maturing quickly, it's time to push the maintainers to add tags to their own packages if they don't have any... you need to coordinate with Enrico Zini to get the information available in a usable form and then make use of it to add a new TODO item in the PTS page.
Line 42: Line 63:
'''Add a bit more stability to links for news''' '''Show sponsored uploads'''
Line 44: Line 65:
Right now we keep the 30 latest news concerning a given package. But the last received news is numbered 1... and the odlest 30. Which means that when the next upload happens, the text which used to be available at 1.html is now at 2.html. When receiving mails from katie extract the gpg signature and show the name of the uploader/sponsor along with Changed-By field.
Line 46: Line 67:
We should at least reverse the numbering and maybe even use a unique number (even if we have to remove old news to avoid letting the PTS grow undefinitely). == PTS rewrite ==
Line 48: Line 69:
'''Keep the first "Accepted" mails'''

Right now the very first "Accepted" mail is dropped because the source package doesn't exist yet (and we can't accept blindly those mails because otherwise one could DoS the PTS by sending many fake "Accepted" mails). Instead of dropping it we should keep it until we have a confirmation that the package has been accepted by ftpmasters (and remove them after XX days if we didn't receive any confirmation).

http://ftp-master.debian.org/~joerg/joey/09.txt is a list of packages that got accepted by ftpmasters during september (change 09 into another number to get the other monthes). We could use that info to see if a "accepted" mail that's waiting can be pushed...
The PTS is being rewritten in order to make it a dynamic Web application. See [[qa.debian.org/distro-tracker]].
----
## This page is referenced from http://packages.qa.debian.org/common/index.html
CategoryPermalink

Package Tracking System (PTS)

Introduction

The Package Tracking System lets you follow almost everything related to the life of a package. It's of interest for co-maintainers, advanced users, QA members, ...

The PTS is actually a website :

You can access information known by the PTS also via a (work in progress) SOAP interface, or the Linked Data interface.

Contributing to the Package Tracking System

How to get the sources ?

$ svn co svn://svn.debian.org/qa/trunk/pts

(you can use svn+ssh://<yourdebianlogin>@svn.debian.org/svn/qa/trunk/pts if you're a Debian developer in the "qa" group and you'll have write access to it)

You can also browse the sources at : http://anonscm.debian.org/viewvc/qa/trunk/pts/

Quick introduction

Raphael Hertzog gave a short overview of the PTS intended for developers. Please check the slides. Some of the information is outdated (for example VERP has been implemented together with a bounce handler) but the basic structure of the software is unchanged.

Actual TODO list

Fix bugs and implement wishlist from the BTS

http://bugs.debian.org/qa.debian.org (those with the "pts" usertag of course : see also: http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=pts&user=qa.debian.org%40packages.debian.org )

Provide RSS feeds for each source package

All the news should be available as an RSS feed. But the RSS feed should be richer: it should integrate more stuff like the upload of a new Ubuntu version with the corresponding Debian patch and also entries for the problems displayed. The difficulty is to have a good date for the various entries that are not tied to an email.

Subscribe to set of packages

The members of the Gnome team would like to subscribe with a single command to all Gnome-related packages. The idea is to add a new "group subscription" feature. The GNOME team maintain the list of packages and anyone can then "groupsubscribe gnome-desktop" and be automatically subscribed to all relevant packages.

This feature could then be used by little "bugsquad team" to quickly move from one package to another.

Possibility to reset keywords to the default state

Right now, once you set some specific keywords on a given source package, you will always have a customized list keyword for this source package. And in some cases, you don't want anymore. A "keywordreset" command would be welcome.

Also te keyword DB is cluttered with wrong email/source package. It should be periodically cleaned of subscriptions which don't exist anymore.

Summary mails sent

Since the beginning, the mail part has support of a "summary" keyword. It was meant to be used to send regular (monthly or quaterly) summary mails repeating the most important information of the webpage and giving statistics about the evolution of the package (number of bugs opened since last summary mail, same for closed, number of uploads, top CVS/SVN committers, top uploaders, ...).

This mail should give some pride to the maintainers who are doing a great work and maybe even create a bit of competition between co-maintainers. :-)

Improve news handling

Each maintainer has the possibility to send (static and usual) news to the PTS. However he can't remove news which are outdated. Because of this, the maintainer is not using this very important feature. This needs to change!

Integrate debtags information

Debtags is maturing quickly, it's time to push the maintainers to add tags to their own packages if they don't have any... you need to coordinate with Enrico Zini to get the information available in a usable form and then make use of it to add a new TODO item in the PTS page.

Show sponsored uploads

When receiving mails from katie extract the gpg signature and show the name of the uploader/sponsor along with Changed-By field.

PTS rewrite

The PTS is being rewritten in order to make it a dynamic Web application. See qa.debian.org/distro-tracker.


CategoryPermalink