[newdak/master] Even more but still only scratching the surface \nSigned-off-by: Joerg Jaspert <joerg@debian.org>

[Joerg Jaspert <joerg@debian.org>]

---
 feature.txt |   40 ++++++++++++++++++++++++++++++++++++++++
 1 files changed, 40 insertions(+), 0 deletions(-)

diff --git a/feature.txt b/feature.txt
index 20d14c7..5ceccda 100644
--- a/feature.txt
+++ b/feature.txt
@@ -19,6 +19,9 @@ When we are done with one, mark it X and add the done date too.
 If you work on something and it takes longer - mark it.
 
 
+Also, do look into old dak doc/TODO, it does have some nice hints what
+to avoid/do.
+
 Global
 ------
 
@@ -115,6 +118,7 @@ DAK server AKA dakd
    (like one package). Instead of current "prepare a file, do a ssh
    push".
 
+
  * Rights management for embargoed issues.  [mhy]  Sat Aug 30 16:26:29 BST 2008
    dakd needs to be able to keep issues embargoed (for security updates)
    on both the filesystem and database levels.  This may mean that most of
@@ -170,3 +174,39 @@ General Archive Issues
    of Debian packages. We shouldn't need a code exception per extra type
    of binary. Maybe it should be handled similar to Formats - using a
    modular structure (if possible at all).
+
+
+ + Have a tool doing a release. [Ganneff]  Thu, 04 Sep 2008 21:13:53 +0200
+   One command "do-release" with some options should create a new
+   [point-]release. Options would be something like from which suite,
+   what stuff, which new version, etc.
+
+
+ + Have a tool for easy archiving. [Ganneff]  Thu, 04 Sep 2008 21:13:53 +0200
+   Same as with release, just in case one wants to move a suite to
+   archive.debian.org. Which might then run dakd too, or dakd
+   needs a way to prepare it for non-dak storage.
+
+
+ * Logging. [Ganneff]  Thu, 04 Sep 2008 21:13:53 +0200
+   Have a nice logger class that can either log to file (default) or
+   syslog (optional). Filename should be able to handle "macro" style,
+   ie. have a name of "/foo/bar/%Y/%M/%D" to have files per day in
+   monthly subfolders of yearly folders. Ie. /foo/bar/2008/08/01
+
+   Also maybe have a different logstyle?
+
+   Have *everything* use this. Including rm.
+
+# From here on I just write down features in a "per tool" based
+# sectioning. Of course this is based on the old dak and the tools we
+# had there. It doesn't neccessarily mean that has to end up in the same
+# way in newdak. But it helps for writing here.
+# [Ganneff]
+
+process-new
+-----------
+
+process-unchecked, process-accepted
+-----------------------------------
+[See above for NiV2 as a general issue touching these]
-- 
1.5.6.3