summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean Finney <seanius@debian.org>2009-09-29 23:59:12 +0200
committerSean Finney <seanius@debian.org>2009-09-29 23:59:12 +0200
commit8042c4ec1e58d4357b6bc7d23cdf83c46a4c17e3 (patch)
tree3e5c936262b1b78d9a4f2938ef0b177e0116e3a4
parentd0b0d57237e9304300244d62aee7f62847dedb61 (diff)
downloadpatch-tracker-8042c4ec1e58d4357b6bc7d23cdf83c46a4c17e3.tar.gz
some small notes in TODO
-rw-r--r--TODO18
1 files changed, 18 insertions, 0 deletions
diff --git a/TODO b/TODO
index 226830d..f0cce67 100644
--- a/TODO
+++ b/TODO
@@ -130,3 +130,21 @@ otherwise differentiating the two. A useful heuristic could be:
Everything else is probably broken packaging and not worth the hassle.
+
+== new "manydiffs" architecture ==
+
+DSA is currently working on creating an official snapshot.debian.org
+service, which contains a historical archive of all packages ever
+uploaded into debian. obviously this has some interesting implications
+for a service like this.
+
+=== Modelling changes ===
+
+the current model is completely release (or ftp-archive) centric,
+where packages are tightly associated with the respective release of
+the package, and information is lost some time after the package is
+superceded or otherwise removed from a debian release (the caching
+implementation extends the life just a bit, but still...). In the
+new system, packages *may* have an association with a specific release,
+or they may not.
+