Differences between revisions 154 and 155
Revision 154 as of 2012-07-04 08:44:08
Size: 8365
Editor: ?DamyanIvanov
Comment: suggest implementing hooks to enforce agreed branch naming policy
Revision 155 as of 2012-07-04 21:05:51
Size: 8427
Editor: ?SalvatoreBonaccorso
Comment:
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
   * build the list of such packages: compare the packages in Git with Sources.gz and check if any of the packages in our repo still has a version in the archive which has the old maintainer    * build the list of such packages: compare the packages in Git with Sources.gz and check if any of the packages in our repo still has a version in the archive which has the old maintainer [[http://lists.debian.org/debian-perl/2012/07/msg00015.html]]

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".

It should have an up to date list of open tasks, please remove completed tasks; for documentation please add links to the History section below (instead of adding them in between the tasks here).

Release-critical bugs

Policy/discussion

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

  • Wheezy freeze and package updates: shall we upload new upstream versions to sid during the freeze?
  • Somewhat related: agree on branch names in git for backports, *-p-u uploads etc. (also add enforcing hooks?)
  • Add handling of debian/copyright (Copyright-Format 1.0) to our group policy.

Transitions

  • perl 5.16 transition: fix bugs: fix bugs and forward upstream, but the transition won't happen in unstable before Wheezy is released

  • Perl4 core libs:

    • deprecated in 5.14, removed in 5.16 => wait for Wheezy release and then NMU the packages that shall be updated (when we have patches)

Packages/tools

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

  • Check the documentation on our website: go through all docs and see if they still apply [gregoa: first round done, handing over to intrigeri]

  • Finish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.):
    • build the list of such packages: compare the packages in Git with Sources.gz and check if any of the packages in our repo still has a version in the archive which has the old maintainer http://lists.debian.org/debian-perl/2012/07/msg00015.html

    • subscribe our -maintainers ML to the PTS of these packages so that we get their bug reports
    • after Wheezy is released: upload these packages, eventually
  • bundle packages: just do it, and see what happens (notes: pkg-components, ftp-master clarification)

  • QA: cast to pointer from integer of different size: file bugs/fix (http://lists.debian.org/debian-perl/2012/02/msg00029.html)

dh-make-perl

  • find a co-maintainer for dh-make-perl
  • continue breaking it into isolated modules
  • improve POD coverage
  • TODO

  • bugs

  • combine dh-make-perl's "refresh" with cme's update functionality

packagecheck{,.pl}

  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl)
    • packagecheck provides some function of "cme check dpkg". It may be better to improve dpkg model taking into account our needs (dod)

  • lintian checks or a lintian vendor profile or something similar; list things we could want to check here:
    • uploading d/changelog with unresolved TODO / WAIT-FOR / etc.

PET

(not exclusively a pkg-perl topic but still)

  • package PET for Debian, so that we can track bugs against it, and so that we can more easily get more instances running => we're less strongly affected by downtimes

    • let's convince Arno to help us [David]
    • Ansgar, what do you think?
  • make it so some more of us have access to the box that runs our PET instance, so that we can repair it when needed
    • on Alioth? first talks pet-team - alioth admins; should happen ~ end of August 2011, but didn't -- status update? [Ansgar]
  • add features we need (Python)
    • track patches
    • others?

Resources:

Recurring tasks

  • Check RFP/ITP packages
  • Yearly cleanup (remove packages from Git that were injected but never finished for upload)
    • retrieve the list is taken from PET ("New packages" section

    • send the list to our mailing-list, with some deadline (example email

    • wait until the deadline expires
    • delete the Git repositories using the remove-repository script

  • Next alioth project member ping: send a "ping" ("Do you still want to be a member?") to those who haven't done something for $time, and remove those who reply with "No" or who don't reply. In order to get a more realistic picture, and maybe also to remove unnecessary permissions. Ansgar has run such a "ping" once (only for non-DD group members, IIRC), and this is a reminder to do it again.

When a new Perl hits unstable

When oldstable is archived

  • Update (build) dependencies. E.g. once Lenny is archived, there's no need for "perl (>= 5.10.1) | libFOO-perl ()" anymore, or to depend on versions of packages that are already satisfied in current stable.

  • "cme fix dpkg-control" should do this ...

Background tasks

Things that would be nice to do, often repetitive. Can be done globally, or every time you work on a specific package.

  • Forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers [tools: forward-bug/forward-patch exists (ghedo++), patchedit exists (jozef++)]
  • Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...) - some stuff fixed, other is more easily fixed by "dh-make-perl --refresh" on the next upgrade ...

Nice to have, some day

  • Write team-specific questions for NM templates (Enrico's mail).

    • Random ideas: fix a Perl bug, update a Perl package to the group standards, adopt a package into the Perl group.
  • NM tasks for teams -- found in an even older mail from Enrico :)

Subpages

History