Extended ZenServerInstance life cycle management

1 files changed, 34 insertions, 0 deletions

diff --git a/TODO.md b/TODO.md
index f1520d2d4..9ea5862f2 100644
--- a/TODO.md
+++ b/TODO.md
@@ -42,3 +42,37 @@
 
 * nodejs/http_parser
 * all the rest (do we need TPS for vcpkg packages?)
+
+
+
+# Productization
+
+* Incremental cook
+* Windows feature complete
+* Mac / Linux support
+* Non-elevated execution
+* State management strategy
+
+# Cache
+
+* M7
+ * Cleanup
+ * Jupiter upstream configuration
+
+# Editor Domain
+
+
+
+
+# Daemon Notes
+
+When operating in background daemon (Windows Service) mode, there are a few
+additional things to consider:
+
+* Install and uninstall (this will vary by platform)
+  * Where is the service installed? How is it uninstalled?
+* Servicing
+  * How is the server versioned? I would suggest going with a single release 
+    number to keep things simple. There should not be any tight coupling with
+    different engine branches (new releases should be backwards compatible) etc
+    and any service development should take place on a single stream