remove completed tasks, add some names
added packagecheck section.
|Deletions are marked like this.||Additions are marked like this.|
|Line 45:||Line 45:|
=== packagecheck ===
* 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.
Debian Perl Group - Open tasks
List of issues that affect our work mode and need discussion.
- Investigate possible migration from Subversion to Git. → Going forward, although nobody here has really worked on a project with thousands of Git submodules
(build-)depending on perl or perl-modules → We should drop the >=5.6 version requirement on perl (cf. #525190), and just specify the version where there is a real requirement. The oldest available release (in oldstable) is 5.8.8 or so
- "Letter to the Perl Community" about Module::Install?
List of tasks that need to be performed on all/many of our packages; or maintainance tools ...
- Create the header/identifier for debian/rules that allows mass-updates. (diocles)
- Rewrite packagecheck (in Perl, modular, maybe not only for pkg-perl) (jeremiah)
- forward all (non Debian specific) patches upstream and add the CPAN RT ids to the patch headers → This can follow DEP3 once it is accepted
we need a tool for easy editing of patch headers according to DEP3
- Fix common lintian-errors repo-wide (e.g. errors from pod2man, missing patch descriptions, ...)
- Policy 3.8.2: 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.
- Change to the unified debian/repack.sh script.
After squeeze: remove (?) B-D on "perl-modules (>= 5.10) | libFOO-perl"
- Upload all half-adopted packages (rationale: old maintainers don't want to get bug reports, we do) → Every adopted package should warrant an immediate upload, as it carries important informations.
→ Damyan is "slowly" (quoting him) but steadily achieving this; he strongly invites us all to participate
=== packagecheck ===
- 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.