Differences between revisions 24 and 25
Revision 24 as of 2011-04-17 15:16:08
Size: 6605
Comment: start a policies section; include question about dual-lived modules
Revision 25 as of 2011-04-18 17:13:52
Size: 6948
Comment: start at some thinking for usertags
Deletions are marked like this. Additions are marked like this.
Line 105: Line 105:

= Bug tagging notes =

We should probably define some useful usertags. Some initial thoughts:

 * Things fixed upstream: tag which (major?) version. Suggested name: fixed-upstream-$maj_ver
 * or only on CPAN: fixed-upstream-cpan
 * Divergence bugs (see above) for all Debian-specific patches:
   * probably different sub-categories?

Some notes/TODO relating to perl interpreter maintenance.

http://lists.alioth.debian.org/pipermail/perl-maintainers/2011-February/001678.html is Niko's Feb 2011 post about work needed.

Dominic Hargreaves will coordinate the perl 5.12/perl 5.14 transition. Please use perl@packages.debian.org as the main contact point.

Work required before perl 5.12 can be uploaded to unstable

  • Check whether it's sensible to upload 5.12 rather than wait for 5.14, given the transition pain. 5.14 due in April 2011

    (see http://perl5.git.perl.org/perl.git/blob_plain/HEAD:/Porting/release_schedule.pod)

    • Look at likely issues for the perl 5.14 transition (will it be lengthy? If so, may be worth getting 5.12 done and dusted first).
  • Rebuild environment for FTBFS bugs (perlapi deps; lib*-perl)
    • mass bug-file; ongoing
  • Removal of things using perl-suid
    • mass bug-file done, just a few left
  • Rebuild environment for FTBFS bugs (Essential packages; all packages?)

Work related to perl 5.12 but not blocking it

Rebuilding packages

The main complication is that we need unofficial binNMUs of the perlapi-* and libperl reverse dependencies so that they can be used as build dependencies for rebuilding the rest.

The scripts at http://svn.debian.org/viewsvn/pkg-perl/scripts/perl-5.10-transition/perlapi.out?view=markup can be used to determine the necessary binNMUs; the order also matters because the dependencies form a chain.

Example: libdevel-caller-perl is needed by libdevel-lexalias-perl, libpadwalker-perl is needed by libdevel-caller-perl etc.

  • set up an sbuild chroot with Perl 5.12 (note that debconf-english may need to be installed manually in place of debconf-i18n so that build-essential stays installable)
  • convert an up to date perlapi.out into sbuild commands like
    • sbuild -c exp -d unstable --make-binNMU="Rebuild for Perl 5.12" --binNMU=1 libgoo-canvas-perl_0.06-1
  • upload the results into an unofficial repository (reprepro is a good tool; maybe the Alioth web space should be used to push these out to public?)
  • file bugs for any failures
  • once all the necessary binNMUs are uploaded, proceed to test rebuild all the arch:all packages (lib*-perl is a first approximation)
  • note that testing on i386 instead of amd64 would be better, as the use64bitint changes in 5.12 only affect 32-bit architectures -> better test coverage

  • a 32-bit chroot and the schroot Personality option should be good enough on an amd64 host

Other issues

  • Switch away from topgit, to git-dpm?

List based on http://lists.alioth.debian.org/pipermail/perl-maintainers/2010-March/001121.html

  • BTS:
    • categorizing and triaging bugs
      • I think usertags could help here, we just need a sensible list
    • closing invalid bugs
      • Eugene has done a lot of this already, but I think there are still plenty left
    • forwarding triaged bugs upstream if they're present on unmodified bleadperl
      • we could definitely do better here; I'm personally erring much too often on the side of "I'll write a patch first" and then forgetting about it
      • OTOH upstream has explicitly stated that documentation bugs should come with patches
    • fixing the `real' Debian-specific bugs
      • this is often hard because perl is such a core package in Debian and needs to change conservatively
      • examples: (495394), (186778)

  • Debian-specific patches (debian/patches/debian/*)
    • document what they do, why they are needed etc.
      • + possibly create one `divergence bug' per patch in the BTS to track this?
  • Alioth infrastructure:
    • sending git commits to the PTS
    • mailing list setup, spam filtering, moderation
      • anything still needed?
    • project web pages and other documentation
      • other than maybe a basic jumping off point pointing to the wiki, PTS etc, what sort of things would go here?
  • general peer review
    • getting git commits via mail should help here

Generic tasks for a new upstream release

TopGit use

Upstream support policy

http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2011-04/msg00352.html

5.10 (in lenny and squeeze) will be desupported by upstream at the release of 5.14. According to my reading of that announcement this will effectively end security support for 5.10 at the same time (since 5.10.0 was released more than three years ago).

Package maintenance policies

  • We only apply patches which have already been applied in bleadperl if at all possible
    • should this include dual-lived modules?

Bug tagging notes

We should probably define some useful usertags. Some initial thoughts:

  • Things fixed upstream: tag which (major?) version. Suggested name: fixed-upstream-$maj_ver
  • or only on CPAN: fixed-upstream-cpan
  • Divergence bugs (see above) for all Debian-specific patches:
    • probably different sub-categories?