the new alpha release is coming out this week sometime. too many

bugs fixed to keep waiting. i still need to track down bug 709
first though, since i am increasingly thinking it's a real bug.


svn:r17944

ChangeLog

-Changes in version 0.2.1.10-alpha - 2009-01-??
+Changes in version 0.2.1.10-alpha - 2009-01-0?
   o Major bugfixes:
     - If the cached networkstatus consensus is more than five days old,
       discard it rather than trying to use it. In theory it could
@@ -30,45 +30,47 @@ Changes in version 0.2.1.10-alpha - 2009-01-??
     - Make get_interface_address() function work properly again; stop
       guessing the wrong parts of our address as our address.
     - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
-      send on that circuit.  Otherwise we might violate the proposal-110
-      limit.  Bugfix on 0.2.1.3-alpha.  Partial fix for Bug 878.  Diagnosis
+      send on that circuit. Otherwise we might violate the proposal-110
+      limit. Bugfix on 0.2.1.3-alpha. Partial fix for Bug 878. Diagnosis
       thanks to Karsten.
     - When we're sending non-EXTEND cells to the first hop in a circuit
-      (for example in order to use an encrypted directory connection), we
-      don't need to use RELAY_EARLY cells: the first hop knows what kind of
-      cell it is, and nobody else can even see the cell type.  This makes
-      it easier to cannibalize circuits like this later.
+      (for example in order to use an encrypted directory connection),
+      we don't need to use RELAY_EARLY cells: the first hop knows what
+      kind of cell it is, and nobody else can even see the cell type.
+      Conserving RELAY_EARLY cells makes it easier to cannibalize circuits
+      like this later.
     - Authorities now list vote for the Stable flag for any router whose
       weighted MTBF is at least 5 days, regardless of the mean MTBF.
     - Stop logging nameserver addresses in reverse order.
-    - If we are retrying something slowly over and over, do not
-      automatically give up after the 254th failure.  Bugfix on
+    - If we are retrying a directory download slowly over and over, do
+      not automatically give up after the 254th failure. Bugfix on
       0.2.1.9-alpha.
     - Do not remove routers as too old if we do not have any consensus
-      document.  Bugfix on 0.2.0.7-alpha.
+      document. Bugfix on 0.2.0.7-alpha.
     - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
-      Spec conformance issue.  Bugfix on Tor 0.0.2pre27.
+      Spec conformance issue. Bugfix on Tor 0.0.2pre27.
     - Resume reporting accurate "stream end" reasons to the local control
       port. They were lost in the changes for Proposal 148. Bugfix on
       0.2.1.9-alpha.
-    - When an exit resolves an address to a local IP, do not just keep
-      retrying that same exit over and over.   Instead, just close
-      the connection.  Addresses bug 872.  Patch from rovv.
+    - When an exit relay resolves a stream address to a local IP address,
+      do not just keep retrying that same exit relay over and
+      over. Instead, just close the stream. Addresses bug 872. Patch
+      from rovv.
     - If a hidden service sends us an END cell, do not consider
-      retrying the connection.  Patch from rovv.
+      retrying the connection; just close it. Patch from rovv.
 
   o Deprecated and removed features:
-    - The old "tor --version --version" command, which would spit out the
-      subversion "Id" of most of the source files, is now removed.  It
+    - The old "tor --version --version" command, which would print out
+      the subversion "Id" of most of the source files, is now removed. It
       turned out to be less useful than we'd expected, and harder to
       maintain.
 
   o Code simplifications and refactoring:
     - Change our header file guard macros to be less likely to conflict
-      with system headers.  Adam Langley noticed that we were conflicting
+      with system headers. Adam Langley noticed that we were conflicting
       with log.h on Android.
-    - Tool-assisted documentation cleanup.  Nearly every function or static
-      variable in Tor should have its own documentation now.
+    - Tool-assisted documentation cleanup. Nearly every function or
+      static variable in Tor should have its own documentation now.
 
 
 Changes in version 0.2.1.9-alpha - 2008-12-25

doc/TODO.future

@@ -49,7 +49,7 @@ Later, unless people want to implement them now:
   - Make the timestamp granularity on logs configurable, with default
     of "1 second".  This might make some kinds of after-the-fact attack harder.
 
-  - We should get smarter about handkling address resolve failures, or
+  - We should get smarter about handling address resolve failures, or
     addresses that resolve to local IPs.  It would be neat to retry
     them, since right now we just close the stream.  But we need to
     make sure we don't retry them on the same exit as before.  But if