summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorSean Finney <seanius@debian.org>2008-06-10 08:06:07 +0200
committerSean Finney <seanius@debian.org>2008-06-10 08:06:07 +0200
commit56cd4ae0bbb2f9fa35e98135fea1f5b2520bd4e5 (patch)
tree3648395b7a7ad5f060c26f9903d24bd4b5980e7a /TODO
parent759695247d3ba69230056429ecad15f672cdd5cd (diff)
downloadpatch-tracker-56cd4ae0bbb2f9fa35e98135fea1f5b2520bd4e5.tar.gz
TODO file updates
Diffstat (limited to 'TODO')
-rw-r--r--TODO20
1 files changed, 20 insertions, 0 deletions
diff --git a/TODO b/TODO
index 284aceb..f0c914f 100644
--- a/TODO
+++ b/TODO
@@ -2,11 +2,26 @@ welcome to the TODO file.
== short-range TODO ==
+fix the patch display/markup
+
+ given the disk space requirements, the patches are not automatically
+ generated any longer. an as-of-yet unwritten cgi script will handle
+ such requests.
+
don't nuke/reinit the whole patch tracking tree
this also implies that some kind of garbage collection takes place
to remove versions that are no longer being tracked
+better handling of more exotic patch systems
+
+ for example:
+ - handling cpp processing of dpatch files
+ - handling wierd configuration for simple-patchsys and recusrive dirs
+ - handling when the directory looks like dpatch/quilt but isn't
+
+code cleanup from really ugly stuff (look for XXX)
+
== medium-range TODO ==
remove all the os.system calls
@@ -18,6 +33,11 @@ make prettier pages
they're all xhtml compliant, using css, and based on a single skeleton
page so it shouldn't be too much work
+decide how much should be cgi-based and how much should be written
+
+ there's no reason why the other pages couldn't also be generated from
+ a cgi, if we desired.
+
== long-range TODO ==
dynamic info?