Hello, The previous week went according to plan; all planned stories were completed:
- The framework for TODOs and problems panels. Allows other modules to provide TODOs/Problems entries which are displayed in the respective panel. - Bug-related todos and problems. A problem entry when there is a the package has a bug tagged "help" and a todo entry when there is a bug tagged "patch". They give the bug counts and links to the BTS. - Lintian summary information. When there are errors or warnings found by lintian, a todo entry is added displaying their counts and appropriate links. A link to the package on lintian.debian.org (on the maintainer's page) is added to the links panel, along with the errors/warnings count if available. - Outdated standards-version warnings. A todo entry when the package's standards version is older than the current Policy version. Additionally, a problems entry if the major version is also older than the current Policy major version number. The current Policy version is retrieved as the version of the debian-policy package in the "default" repository; it is no longer hardcoded as in the current PTS. - Testing migration status information. The "testing migration" panel (as in the current PTS) which shows any migrations that the package is part of. Additionally, any excuses [1] are also extracted and displayed with links to other packages being replaced to link to the matching PTS page. - Collect news by email. Allows creating news from received emails. Any emails passed to this management command with the X-PTS-Package header create a news for the package given in that header automatically, with the content of the news being the message itself. It is also allowed for vendors to implement a function which provides news items for received emails, based on their own rules. Also, thanks to the previous work on the news framework, any inline signatures in the emails are extracted automatically. For Debian, news items are created for accepted source packages, dak rm emails, and testing watch package emails. As always, you can see this deployed on pts.debian.net. For now, the plan for next week is shorter by one workday, since the weekly meeting with my mentors is scheduled a day earlier, as they are not able to attend in the usual time due to debconf. The next report will include any possible extra stories which are finished in the meantime. The stories planned are: - Create a framework for an "action needed" panel. Even though the stories implemented and described above regarding package todos and problems mirror the current PTS, we want to take this rewrite opportunity to make some improvements. The todos and problems are going to be consolidated into a single "action needed" panel. Each item will also be stored in the database, thereby allowing other modules to use the data, e.g. filtering by problem type and displaying each package with that particular problem. Also, the displayed text will be made shorter than it currently is, giving only the most important information. A more detailed description can be provided and appears in a popup when the user clicks on a question mark next to the short description. (If Javascript is disabled, a new page is opened.) - Migrate the currently implemented todos/problems to the "action needed" panel. - Build log check information. Provide links to buildd and clang build logs in the links panel. Add an action needed entry if there are any errors or warnings found in buildd logcheck data. - Watch file scanner information summary. Add an action needed entry if there is a newer package version upstream. An action needed entry is also added if the package's watch file is broken and if there is a new watch file available. That's it for now. Thanks for reading. Cheers, Marko [1] http://ftp-master.debian.org/testing/update_excuses.html -- Marko Lalić email: [email protected] mobile: +387 61 817 681 _______________________________________________ Soc-coordination mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination
