Differences between revisions 21 and 22
Revision 21 as of 2009-03-12 20:53:35
Size: 2191
Editor: ?GregorHerrmann
Comment: add some more tasks ...
Revision 22 as of 2009-03-13 12:48:02
Size: 2404
Editor: ?DamyanIvanov
Comment: add dh-make-perl sub-section
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
=== dh-make-perl ===

 * continue breaking it to isolated modules
 * make POD coverage pass (by completing the docs)
 * make --refresh also update (or at least check&warn) dependencies (and their versions)

?TableOfContents(2)

Debian Perl Group - Open tasks

This page collects ideas for tasks within the ["Teams/DebianPerlGroup"]. These tasks can be worked on at DebCamp or might be tackled by volunteers "at home".

History

Policy/discussion

List of issues that affect our work mode and need discussion.

  • -

Packages/tools

List of tasks that need to be performed on all/many of our packages; or maintainance tools ...

  • Work out how the applications "branch"/git repo really works.
  • Finish or just use the "unified" debian/rules (for packages with and without quilt).
  • Create the header/identifier for debian/rules that allows mass-updates.
  • Clean up the "New Packages - Work in Progress" (i.e. never uploaded) list of packages in PET.
  • Review the "Newer upstream available - Work in Progress" section in PET and file ITPs for missing packages etc.
  • Rename all source packages to lib*-perl.
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl)
  • Forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers.
  • Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...)
  • Investigate possible migration from Subversion to Git
  • Policy 3.8.1: mass update packages?
  • Lenny is out!
    • remove transitional dummy packages
    • remove (?) B-D on "perl-modules (>= 5.10) | libFOO-perl"

  • Patches: forward them upstream; maybe we need a tool?

dh-make-perl

  • continue breaking it to isolated modules
  • make POD coverage pass (by completing the docs)
  • make --refresh also update (or at least check&warn) dependencies (and their versions)

Others

Topics that don't fit in the above categories.

  • debian/copyright:
    • boilerplate for reference to changelog
    • mechanism for members to accept this procedure