Differences between revisions 136 and 137
Revision 136 as of 2012-06-05 19:39:52
Size: 6262
Editor: ?GregorHerrmann
Comment: add link to perl 5.16 transition bugs
Revision 137 as of 2012-06-06 17:39:43
Size: 6517
Editor: ?IntRigeri
Comment: Start reorganizing stuff
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
 * wheezy freeze and package updates  * Wheezy freeze and package updates: shall we upload new upstream versions to sid during the freeze?
   See [[https://lists.debian.org/debian-perl/2010/08/msg00038.html|Minutes from the meeting at DebConf in 2010]], point 4.
Line 35: Line 36:
 * [[DebianPerlGroup/OpenTasks/Applications|Maintenance of applications in the Debian Perl Group]] -- included in our [[http://pkg-perl.alioth.debian.org/policy.html#package_naming_policy|Policy]] already, there are some packages that still need adjustment (→ file bugs with usertags)
 * Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl; see also below) (jeremiah) ''packagecheck provides some function of "cme check dpkg". It may be better to improve dpkg model taking into account our needs (dod)''
 * Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl; see also the section dedicated to packagecheck below) (jeremiah) ''packagecheck provides some function of "cme check dpkg". It may be better to improve dpkg model taking into account our needs (dod)''
Line 40: Line 40:
 * Policy 3.8.4: mass update packages? Very old standards-versions might warrant (just for QA work) to be updated, as they were built with very old toolchains. We should at least check packages that have not been updated since Sarge release. (fabreg)
Line 43: Line 42:
 * Next alioth project member ping
 * perl 5.12 transition: fix [[http://deb.li/uj2v|bugs]], change some (build) dependencies after 5.12 hits unstable (should be done, is there something left?)
 * perl 5.14 transition: fix [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.14-transition;users=debian-perl@lists.debian.org|bugs]], change some (build) dependencies later (should be done, is there something left?)
Line 47: Line 43:
 * Check the documentation on [[http://pkg-perl.alioth.debian.org/|our website]].
 * Polic
y 3.9.1 (and base-files) has introduced /usr/share/common-licenses/GPL-1. [[http://bugs.debian.org/436105|#436105]]
 * Check RFP/ITP packages
 * F
inish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.) (is there something left?)
 * Check the documentation on [[http://pkg-perl.alioth.debian.org/|our website]]: go through all docs and see if they still apply [gregoa]
 * Finish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.): check if there is something left, by comparing 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.
Line 52: Line 46:
 * After the alioth changes: what needs to be done? (Vcs-* headers? documentation? website? scripts?) (is there something left?)
Line 55: Line 48:
 * Multi-arch / cross-building (?)  * Multi-arch / cross-building: check if and how we are affected.
Line 81: Line 74:
=== Subpages === == Recuring tasks ==

 * Check RFP/ITP packages
 * 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 ===

 * change some (build) dependencies ("libFOO-perl (>= x.y) | perl (>= 5.1x)" that can be turned around); So this is a simple grep + sed or similar over all our packages and a friendly mass-commit.

=== 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" may help, although it's a bit slow for all packages...)

== Subpages ==

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

History

Policy/discussion

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

Transitions

Packages/tools

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

  • Post svn->git migration tasks/tools/docs

    • docs:
      • (maybe) tips.pod
      • [howto/quilt-copyable.pod *cough*]
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl; see also the section dedicated to packagecheck below) (jeremiah) packagecheck provides some function of "cme check dpkg". It may be better to improve dpkg model taking into account our needs (dod)

  • Patches:
    • 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 ...

  • After squeeze is archived: remove alternative dependencies / versioned dependencies that refer to oldstable can be done by "cme fix dpkg"

  • Next summer cleanup (remove packages from svn that were injected but never finished for upload)
  • perl 5.16 transition: fix bugs

  • Check the documentation on our website: go through all docs and see if they still apply [gregoa]

  • Finish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.): check if there is something left, by comparing 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.
  • bundle packages: get out of the insanity :) (notes: pkg-components, ftp-master clarification)

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

  • NM tasks for teams -- found in an even older mail from Enrico :)

  • Multi-arch / cross-building: check if and how we are affected.
  • 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

  • continue breaking it to isolated modules
  • make POD coverage pass (by completing the docs)
  • TODO

  • bugs

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

packagecheck{,.pl}

  • review the code that Jeremiah has written to see if it fits our needs
  • suggestions for more functionality, feedback, etc.
  • both files are in the scripts repo

PET

(not exclusively a pkg-perl topic but still)

  • it's PET3 in the meantime :)

  • PET project's repo: git+ssh://git.debian.org/git/pet/pet3.git

  • PET3: maybe setup another instance (fallback?)
  • PET3 on Alioth; first talks pet-team - alioth admins; should happen ~ end of August 2011, but didn't
  • web: http://pet.debian.net/pkg-perl/pet.cgi

Recuring tasks

  • Check RFP/ITP packages
  • 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

  • change some (build) dependencies ("libFOO-perl (>= x.y) | perl (>= 5.1x)" that can be turned around); So this is a simple grep + sed or similar over all our packages and a friendly mass-commit.

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" may help, although it's a bit slow for all packages...)

Subpages

Comparison