[SCM] Debian package checker branch, master, updated. 2.1.3-65-ge8fe74e
The following commit has been merged in the master branch:
commit 24f25d8f2d19deb710e462c40de40166a26a3359
Author: Russ Allbery <rra@debian.org>
Date: Thu Jan 1 12:11:36 2009 -0800
Update the TODO file
Add test suite changes from my recent message, update milestones, add
Lintian manual changes, and remove stuff that's now done or that no
longer seems to apply (old Policy comments, for example),
diff --git a/private/TODO b/private/TODO
index b94b9fc..1566413 100644
--- a/private/TODO
+++ b/private/TODO
@@ -1,7 +1,7 @@
Not intended for single bug fixes, use the confirmed and owner tags
in the BTS, but for somewhat bigger tasks
-goals for 2.0.0
+goals for 2.2.0
===============
- go through all checks and try to move common code to modules
@@ -9,7 +9,11 @@ goals for 2.0.0
- overhaul the Errors/Warnings concept (#243976)
-- mostly done
We still need official support for alternative output formats.
- The current stuff is still experimental. [2.1.0?]
+ The current stuff is still experimental. [2.2.0?]
+- add additional test suite types
+ + normal TAP-style Perl tests
+ + raw directories for building Debian packages via dpkg -b
+ + changes files
goals not targetted
===================
@@ -21,6 +25,12 @@ goals not targetted
references have them, and more generally that appropriate references are
present
- remove old unbalance `' quotes from all tag descriptions
+- rewrite the Lintian manual in something other than DebianDoc-SGML
+- update the Lintian manual
+ + document severity/certainty
+ + document other output formats
+ + document the reporting framework
+ + developer documentation of the test suite, submitting patches, etc.
goals outside of the lintian source
===================================
@@ -36,19 +46,6 @@ goals outside of the lintian source
old todo list
=============
-reorganize regression suite:
- valid
- invalid
- <in between, odd, etc>
-
- whenever a check is touched or added, add a valid and invalid example
-
rewrite into a more sane layout. What I would really like is a set of modules
that the controller script can open and use. Probably some OO design.
I am leaning towards python, but will give OO perl a look first.
-
-various items require the policy team to make a new policy or update existing
-need to keep on them about this
- * libs v. plugins
- * X policy
-
--
Debian package checker
Reply to: