[Soc-coordination] [Package Tracking System rewrite] Week 7 - August 2 - Status Report

[Marko Lalic]

Hello,

Last week all planned stories were completed. Those are:

- Bug statistics on package pages - the bugs panel. It is implemented
in a way to allow various customization options to vendors. The
simplest way is to provide the data (bug categories and bug counts per
category) in the database. Alternatively, a vendor-specific function
which gives a list of category/count which should be displayed will
take precedence. Finally, the most complex is to provide a new
template if the vendor so requires. This last option is used for
Debian's implementation which gives the number of merged bugs for each
category.
The statistics are also displayed for the binary packages (in the
binaries panel).

- Generate news from monitored repositories. News are generated when a
new package version appears in any repository, when an existing
package version appears in a new repository and when a package version
is removed from a repository. For the "new version" news, the
changelog entry for the version is extracted and included in the news
content. The signer of the package is also displayed in the news.

- Framework for version-specific links - versioned links panel. A new
panel which should display links for all versions of a package (in all
repositories). The links for each package are extensible by
implementing a "LinkProvider" class. The link to the .dsc file is
moved from the binaries panel to this new panel.

- Extracted filers: changelog, copyright, rules, control. The PTS
downloads the source package and extracts the aforementioned files and
saves them as media assets. Links to these files are provided in the
versioned-links panel. For packages with 3.0 (quilt) format, only the
.debian.tar.* file is downloaded in order to extract the wanted files,
so as to decrease the amount of work (download size).

The week also included some work on the page's visual formatting such
as adding a scrollbar for panels with a large number of items (such as
the binaries panel), etc.

This is all currently deployed and you can see it in action at
http://pts.debian.net

Next week's plan is to work on the following stories:

- Collect news by email. Email messages sent to a well-known address
conforming to certain rules regarding their content/headers are turned
into news items.

- Framework for todos & problems. Implement a way for different
modules to include their own todos/problems for packages.

- Testing migration status information - the testing migration panel.
Provides information about which transitions the package is part of
and any existing excuses. (Debian specific feature)

- Bug-related todos and problems. If the package has any bugs tagged
patch or help, a todo or problems item is included, respectively.
(Debian specific feature)

- Lintian summary information - if there are any lintian problems or
warnings, a link to the links panel and a todo entry are added.
(Debian specific feature)

-  Outdated standards-version warning. If the package's
Standards-Version is older than the current Policy version, a todo
entry is added. If the package's Standards-Version major version
number differs from the current Debian Policy major version number, a
problem is added. The policy version to be compared against is
extracted from the debian-policy source package in the default
repository.

Thanks for reading another report.

Cheers,

-- 
Marko Lalić

email: marko.lalic at gmail.com
mobile: +387 61 817 681
web: www.eestec-sa.ba