+Add a suite (origin=, label= and codename= are optional)
+signingkey= will ensure that Release files are signed
+# dak admin suite add-all-arches unstable x.y.z origin=MyDistro label=Master codename=sid signingkey=DDDDDDDD
+
+Add the components to the suite
+# dak admin s-c add unstable main contrib non-free
+
+Re-run dak init-dirs to add new suite directories to /srv/dak
+# dak init-dirs
+
+#######################################################################
+# Example package flow
+#######################################################################
+
+For this example, we've grabbed and built the hello source package
+for AMD64 and copied it into /srv/dak/queue/unchecked.
+
+We start by performing initial package checks which will
+result in the package being moved to NEW
+# dak process-upload -d /srv/dak/queue/unchecked
+
+-----------------------------------------------------------------------
+hello_2.6-1_amd64.changes
+
+hello (2.6-1) unstable; urgency=low
+ .
+ * New upstream release.
+ * Drop unused INSTALL_PROGRAM stuff.
+ * Switch to 3.0 (quilt) source format.
+ * Standards-Version: 3.9.1 (no special changes for this).
+
+source:hello
+binary:hello
+
+binary:hello is NEW.
+source:hello is NEW.
+
+[N]ew, Skip, Quit ? N
+ACCEPT-TO-NEW
+Installed 1 package set, 646 KB.
+-----------------------------------------------------------------------
+
+We can now look at the NEW queue-report
+# dak queue-report
+-----------------------------------------------------------------------
+NEW
+---
+
+hello | 2.6-1 | source amd64 | 42 seconds old
+
+1 new source package / 1 new package in total / 0 new package to be processed.
+-----------------------------------------------------------------------
+
+And we can then process the NEW queue:
+# dak process-new
+
+-----------------------------------------------------------------------
+hello_2.6-1_amd64.changes
+-------------------------
+
+ Target: unstable
+ Changed-By: Santiago Vila <sanvila@debian.org>
+
+NEW
+
+hello optional devel
+dsc:hello extra misc
+Add overrides, Edit overrides, Check, Manual reject, Note edit, Prod, [S]kip, Quit ?A
+PENDING ACCEPT
+-----------------------------------------------------------------------
+
+At this stage, the package has been marked as ACCEPTed from NEW.
+We now need to process the NEW policy queue:
+
+# dak process-policy new
+-----------------------------------------------------------------------
+Processing changes file: hello_2.6-1_amd64.changes
+ ACCEPT
+-----------------------------------------------------------------------
+
+We can now see that dak knows about the package:
+# dak ls -S hello
+
+-----------------------------------------------------------------------
+ hello | 2.6-1 | unstable | source, amd64
+-----------------------------------------------------------------------
+
+# dak control-suite -l unstable
+
+-----------------------------------------------------------------------
+hello 2.6-1 amd64
+hello 2.6-1 source
+-----------------------------------------------------------------------
+
+Next, we can generate the packages and sources files:
+# dak generate-packages-sources2
+(zcat /srv/dak/ftp/dists/unstable/main/binary-amd64/Packages.gz for instance)
+
+And finally, we can generate the signed Release files:
+# dak generate-release
+
+-----------------------------------------------------------------------
+Processing new
+Processing byhand
+Processing unstable
+-----------------------------------------------------------------------
+(Look at /srv/dak/ftp/dists/unstable/Release, Release.gpg and InRelease)
+
+
+#######################################################################
+# Next steps
+#######################################################################
+
+The debian archive automates most of these steps in jobs called
+cron.unchecked, cron.hourly and cron.dinstall.
+
+TODO: Write example (simplified) versions of these cronjobs which will
+do for most installs.