[Piuparts-commits] [piuparts] 01/07: cleanup TODO

Holger Levsen holger at moszumanska.debian.org
Mon Feb 17 23:15:57 UTC 2014


This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch develop
in repository piuparts.

commit a55bc6f774570c94ff20cba6c45d183a060e6084
Author: Holger Levsen <holger at layer-acht.org>
Date:   Mon Feb 17 22:52:12 2014 +0100

    cleanup TODO
---
 TODO | 55 ++++++++++++++++++++++++-------------------------------
 1 file changed, 24 insertions(+), 31 deletions(-)

diff --git a/TODO b/TODO
index 24d576d..431fc82 100644
--- a/TODO
+++ b/TODO
@@ -30,6 +30,9 @@ for 0.5x:
 - Documentation related:
   - examples are duplicated in piuparts.1.txt and README.txt - only keep one copy.
   - README_server has some duplication information on configuration as well.
+  - link wiki:piuparts/UseCases||UsageTips in README_1st (after we agreed on a name)
+  - add a sample config with all possible keys set to some useful value
+    (like /usr/share/doc/apt/examples/configure-index.gz)
 
 - more stats and graphs:
   - packages processed per day and section
@@ -41,23 +44,26 @@ for 0.5x:
     squeeze, wheezy, jessie, sid.
   - move counts.txt from htdocs to master.
 
-- add a sample config with all possible keys set to some useful value
-  (like /usr/share/doc/apt/examples/configure-index.gz)
-
 - piuparts.conf.pejacevic: use mirror via nfs (faster)
 
 - look for a solution to use the global debian mirror for debian-backports,
   too, to avoid hardcoding a specific mirror in distros.conf
 
-- install from git/Makefile: remove the need for /etc/piuparts
-
 - maybe compress all logfiles
 
-- link wiki:piuparts/UseCases||UsageTips in README_1st (after we agreed on a name)
-
 
 for 0.6x:
 
+- really support multiple architectures:
+  - piuparts-report should have a list of available arch and list packages only
+    available on untested archs in a new state
+    "(depends-)not-available-on-tested-archs"
+  - master should (per default) only schedule packages which are not available
+    on the master arch to slaves of different archs ->
+    "schedule-evenly-to-slaves = no"
+
+- piuparts-master: keep track of to whom a reservation was given
+
 - if it weren't for 'slave-bin/slave_cleanup', the slave would only need
   rights to run "sudo piuparts" but nothing else. If we can clean this up,
   the sudoers.d should recommend sudo (lsof|kill|umount) for admins.
@@ -85,17 +91,14 @@ for 0.6x:
     generate _issues.tpl (pass/) and/or _error.tpl (fail/ bugged/ affected/)
   - rework known problems to a python-friendlier format
 
+- install from git/Makefile: remove the need for /etc/piuparts
+
 - accept a PIUPARTS_CONF environment variable everywhere to point to a different
   piuparts.conf
 
 - write reportbug-like wrapper for mass bug filing (start simple, make it more
   sophisticated later).
 
-- rewrite piuparts-analyze to run over all sections and cache BTS responses
-
-- "decorate" (strike-through) bug links generated by piuparts-analyze to
-  indicate resolved state (take package version into account!)
-
 - verify that find_default_debian_mirrors does something sane
 
 - find_default_debian_mirrors: if parts[2] contains a / (think stable/updates
@@ -122,6 +125,11 @@ for 0.7x and later:
 - mounting /proc and perhaps others (usbfs, sysfs, /dev/pts, etc.) in the chroot
   might be a good idea because some packages might need this.
 
+- rewrite piuparts-analyze to run over all sections and cache BTS responses
+
+- "decorate" (strike-through) bug links generated by piuparts-analyze to
+  indicate resolved state (take package version into account!)
+
 - report:
   - write stats about the reasons for failures, as its done with shell scripts
     now (piuparts-analyze.py is an existing "fragment".)
@@ -133,16 +141,6 @@ for 0.7x and later:
 - a redirect of http://piuparts.d.o/foo to http://p.d.o/source/f/foo.html would
   be nice
 
-- really support multiple architectures:
-  - piuparts-report should have a list of available arch and list packages only
-    available on untested archs in a new state
-    "(depends-)not-available-on-tested-archs"
-  - master should (per default) only schedule packages which are not available
-    on the master arch to slaves of different archs ->
-    "schedule-evenly-to-slaves = no"
-
-- piuparts-master: keep track of to whom a reservation was given
-
 - piuparts can't currently test upgrades of required packages.  (Because they
   cannot be removed, it assumes these are untestable, which is only true for
   removal tests...
@@ -157,12 +155,7 @@ for 0.7x and later:
 
 - move shell cronjobs functionality into master, slave & report
 
-
-1.0 should really have automated testing of piuparts itself...
------------------------------------------------------------------
-
-- create archive of broken packages to provide test cases for piuparts testing.
-
-- create emacspeak-broken-dpkg-preconfigure package for broken repo. (then later
-  put more broken packages in there and use that for testing piuparts)
-
+- automated testing of piuparts using an archive of known broken packages:
+  - create archive of broken packages to provide test cases for piuparts testing.
+  - create emacspeak-broken-dpkg-preconfigure package for broken repo. (then later
+    put more broken packages in there and use that for testing piuparts)

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/piuparts/piuparts.git



More information about the Piuparts-commits mailing list