1 Not intended for single bug fixes, use the confirmed and owner tags
2 in the BTS, but for somewhat bigger tasks
7 - go through all checks and try to move common code to modules
9 - overhaul the Errors/Warnings concept
11 -- will make a proposal after 1.23.1 is released, djpig
12 -- rra: I think we need to classify tags on three axes:
13 --- source of check (policy, devref, library, utility man page)
14 --- reliability (how sure is lintian the problem is present)
15 --- severity (how big of a problem is this)
16 where the last corresponds to the current errors/warnings concept and
17 the others aren't currently present. We then need to allow users to
18 select what they want to see based on any of the three criteria; for
19 instance, ftp-master may want to run lintian in a mode that only does
20 Policy and "package would be broken" checks with severity error and
21 the top reliability rating.
26 - #118170: [frontend] lintian needs lots of space in /tmp
27 should be tackled, don't know when, though
28 - go through the test suite and organise it more cleanly
29 - update doc/CREDITS file
30 - Go through testset/libbaz/debian/rules, and make sure all TODO's are
32 - go through all tags and make sure that any that should have Policy
33 references have them, and more generally that appropriate references are
35 - remove old unbalance `' quotes from all tag descriptions
37 goals outside of the lintian source
38 ===================================
40 - get lintian.debian.org working again with the current lintian
41 - set up system for automatically filing bugs based on specific lintian
42 tags (the most reliable ones), with usertags to ensure the bugs aren't
44 - set up lintian for use on ftp-master so that it can be used to
45 automatically REJECT packages with particular errors. will require a
46 mode that only runs important checks that are highly reliable
51 reorganize regression suite:
54 <in between, odd, etc>
56 whenever a check is touched or added, add a valid and invalid example
58 rewrite into a more sane layout. What I would really like is a set of modules
59 that the controller script can open and use. Probably some OO design.
60 I am leaning towards python, but will give OO perl a look first.
62 various items require the policy team to make a new policy or update existing
63 need to keep on them about this