[or-cvs] more todo items as we get closer to 0.1.1 final

[arma@xxxxxxxx]

Update of /home2/or/cvsroot/tor/doc
In directory moria:/home/arma/work/onion/cvs/tor/doc

Modified Files:
	TODO 
Log Message:
more todo items as we get closer to 0.1.1 final


Index: TODO
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.401
retrieving revision 1.402
diff -u -p -d -r1.401 -r1.402
--- TODO	10 Jan 2006 22:05:31 -0000	1.401
+++ TODO	11 Jan 2006 23:27:47 -0000	1.402
@@ -34,11 +34,16 @@ Website:
     stickers directly, etc.
 
 for 0.1.1.x:
+  - Mysterious crash for fast servers: Bug 234.
+R - hidden service accesses can crash sometimes: Bug 220.
+  - Make "setconf" and "hup" behavior cleaner for LINELIST config
+    options (e.g. Log). Bug 238.
+R - We should do address rewriting after the controller sends us an
+    "attachstream 0": Bug 225.
+
 N - if they're trying to be a tor server and they're running
      win 98 or win me, give them a message talking about The Bug.
 
-R . Rename 'helper' to 'guard'.
-
 N - Display the reasons in 'destroy' and 'truncated' cells under some
     circumstances?
 
@@ -64,15 +69,20 @@ R - When we connect to a Tor server, it 
     - Specify
     - Implement
 
-R - clients prefer to avoid exit nodes for non-exit path positions.
-
   - find 10 dirservers.
+    - Make it no longer default for v2 dirservers to support v1.
     - What are criteria to be a dirserver?  Write a policy.
 
-  - the tor client can do the "automatic proxy config url" thing?
+
+
+
 
 Deferred from 0.1.1.x:
 
+  - the tor client can do the "automatic proxy config url" thing?
+
+R - clients prefer to avoid exit nodes for non-exit path positions.
+
   - Automatically determine what ports are reachable and start using
     those, if circuits aren't working and it's a pattern we recognize
     ("port 443 worked once and port 9001 keeps not working").