speed up reliability

[oweals/gnunet.git] / TODO

diff --git a/TODO b/TODO
index 5e68b7a51a20c853f75e3c4089eeb3c4618b9dce..3607193e34fd9f0e3eb99abc13447b3eb04a9632 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,29 +1,22 @@
-0.9.0pre3:
-* clean buildbots (with new transport)
-
-0.9.0pre4:
+0.9.0:
 * GNUNET-GTK: [CG]
-  - figure out where in the GUI we should show active upload operations and allow aborts
-  - handle events:
-    + search error
-    + publish error
-* NAT:
-  - support HOSTNAME given for external-IP address (dyndns!)
+  - provide context menus to allow aborts of downloads/uploads
+  - provide way to handle errors (search, download, publish errors)
+* new webpage:
+  - write chapter on DHT/block [Nate] 
+  - make a NICE download page 
+* big code review
+* Determine RC bugs and fix those (release should have no known real bugs)
+* Transport:
+  - When receiving SESSION_CONNECT: actually consider switching session
+    (test this!)
 * FS [CG]
   - implement multi-peer FS performance tests + gauger them!
     + insert
     + download
     + search
-* transport:
-  - explicit DISCONNECT: add signature, create message...
-  - CONNECT: actually consider switching session...
-
-0.9.0:
-* new webpage:
-  - write chapter on DHT/block [Nate] 
-  - make a NICE download page 
-* big code review
-* Determine RC bugs and fix those  (release should have no known real bugs)
+* blocks:
+  + should block plugins live in block/ or with fs/dht/vpn?
 
 0.9.1:
 * TRANSPORT: [MW]
@@ -31,7 +24,7 @@
     queue of size > 2), might be better to have at MOST one message pending
     per plugin/target and only send the next one after the continuation was
     called (or use 'notify_transmit_ready-style API?)
-  - WLAN transport backend [DB]
+  - WLAN transport backend (code cleanup) [MW]
   - need to periodically probe latency/transport cost changes & possibly switch transport 
     (working ATS)
 * DV: