Differences between revisions 91 and 94 (spanning 3 versions)
Revision 91 as of 2011-07-18 14:16:31
Size: 7012
Editor: ?GregorHerrmann
Comment: note 2 "projects" are started
Revision 94 as of 2011-07-19 09:52:23
Size: 7173
Editor: ?GregorHerrmann
Comment: move package naming task from discussion to package section (nothing to discuss), reword slightly
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * [[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, might need work
Line 23: Line 22:
 * Which tests do we run / which variables do we set? → consistency over packages. Discussion started on the [[http://lists.debian.org/debian-perl/2011/07/msg00031.html|mailing list]].
Line 42: Line 42:
 * [[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)
Line 61: Line 62:
 * Which tests do we run / which variables do we set? -> consistency over packages
Line 65: Line 65:
 * Read [[http://fedoraproject.org/wiki/Packaging/Perl|Fedora Perl Packaging Policy]] and compare with ours.
Line 91: Line 90:
== Comparison ==
 * [[http://fedoraproject.org/wiki/Packaging/Perl|Fedora Perl Packaging Policy]]

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.

  • Handling of removed (from unstable) packages: remove from trunk or also from branches/tags? move to attic? something else? At the moment we are a bit inconsistent. -- There's also `rm-pkg-from-repo' in our scripts directory.
  • Which tests do we run / which variables do we set? → consistency over packages. Discussion started on the mailing list.

Packages/tools

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

  • Investigate possible migration from Subversion to Git
    • - PET2 is ready? - Migration tasks/tools
      • there is a git repo
        • git.debian.org:/git/pkg-perl/tools/svn-git-migrate.git
        • to collect scripts and documents in progress.
      • svn-all-fast-export config (generated by script, db to handle)
        • - svn-all-fast-export now available on vasks, thanks to Mithrandir.
      • pristine-tar import (from snapshots.d.o?)
      - Post Migration tasks/tools/docs
      • create repo tool (remote-ize setup repo) -> alioth-git-repo (in svn/scripts, uses /git/pkg-perl/setup-repository on vasks)

      • mr config management (CGI?)
      • update docs for how to create/checkout mass-checkout repos
  • Maintenance of applications in the Debian Perl Group -- included in our Policy already, there are some packages that still need adjustment (→ file bugs with usertags)

  • Create the header/identifier for debian/rules that allows mass-updates. (diocles)
  • Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl; see also below) (jeremiah)
  • Patches:
    • forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers; wait for DEP3 to be finalised? write a nice bug/patch forwarding helper tool; first versions of forward-bug/forward-patch exist (ghedo++)
    • we need a tool for easy editing of patch headers according to DEP3; first version of 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 ...

  • 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)
  • After squeeze: remove B-D on "perl (>= 5.10) | libFOO-perl"

  • After squeeze: remove transitional dummy packages (and debian/TODO items for them)
  • After squeeze: remove alternative dependencies / versioned dependencies that refer to oldstable (etch)
  • Next summer cleanup (remove packages from svn that were injected but never finished for upload); started 2011-07-18
  • Next alioth project member ping
  • perl 5.12 transition: fix bugs, change some (build) dependencies after 5.12 hits unstable (partly done)

  • perl 5.14 transition: fix bugs, change some (build) dependencies later

  • Check the documentation on our website.

  • Policy 3.9.1 (and base-files) has introduced /usr/share/common-licenses/GPL-1. #436105

  • Check RFP/ITP packages
  • Finish uploading packages where the version in the archive doesn't have the group as the maintainer (i.e. adopted packages etc.)
  • bundle packages: get out of the insanity :) (notes: pkg-components, ftp-master clarification)

  • Maybe add debian/source/local-options with unapply-patches and abort-on-upstream-changes to all packages? (packagecheck, see also below) -- might be unnecessary if dpkg changes its defaults, cf. recent (May 2011) discussions on debian-devel@l.d.o

  • Switch modules and tools to use Digest::SHA instead of Digest::SHA1 and remove libdigest-sha1-perl from the archive #594273 Transitions/DigestSHA1ToDigestSHA (http://deb.li/digestsha)

  • Check for duplicate packages in svn and git; started 2011-07-18
  • After the alioth changes: what needs to be done? (Svn-* headers? documentation? website? scripts?)
  • Team-specific questions for NM templates (Enrico's mail).

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}

  • discuss git support and way forward
  • review the code that Jeremiah has written to see if it fits our needs
  • suggestions for more functionality, feedback, etc.

PET

(not exclusively a pkg-perl topic but still)

  • multi-repo support? --> already in PET2

  • merge ansgar's PET2? (demo, repo) -- it's now in the PET project's repo: git+ssh://git.debian.org/git/pet/pet2.git

  • PET2: maybe setup another instance
  • PET2 on Alioth?

Comparison