[or-cvs] [tor/master] prepare the 0.2.2.13-alpha changelog

[arma at torproject.org]

Author: Roger Dingledine <arma at torproject.org>
Date: Fri, 23 Apr 2010 20:59:20 -0400
Subject: prepare the 0.2.2.13-alpha changelog
Commit: 8afc7d563ded50d6813ddf15a441b0063c6c0477

---
 ChangeLog                               |   26 ++++++++++++++++++++++++++
 changes/close_begindir_circs            |    7 -------
 changes/close_idle_conns_faster         |    6 ------
 changes/immediate_reachability_check    |    7 -------
 changes/kill_clique_mode                |    4 ----
 changes/no_reachability_test_on_startup |    6 ------
 6 files changed, 26 insertions(+), 30 deletions(-)
 delete mode 100644 changes/close_begindir_circs
 delete mode 100644 changes/close_idle_conns_faster
 delete mode 100644 changes/immediate_reachability_check
 delete mode 100644 changes/kill_clique_mode
 delete mode 100644 changes/no_reachability_test_on_startup

diff --git a/ChangeLog b/ChangeLog
index b7b24da..eece4f7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,29 @@
+Changes in version 0.2.2.13-alpha - 2010-04-24
+  o Major bugfixes:
+    - Relays now close idle circuits early if it looks like they were
+      intended for directory fetches. Relays are also more aggressive
+      about closing TLS connections that have no circuits on them. Such
+      circuits are unlikely to be re-used, and tens of thousands of them
+      were piling up at the fast relays, causing the relays to run out
+      of sockets and memory. Bugfix on 0.2.0.22-rc (where clients started
+      tunneling their directory fetches over TLS).
+
+  o Minor features:
+    - Finally get rid of the deprecated and now harmful notion of
+      "clique mode", where directory authorities maintain TLS connections
+      to every other relay.
+    - Directory authorities now do an immediate reachability check as soon
+      as they hear about a new relay. This change should slightly reduce
+      the time between setting up a relay and getting listed as running
+      in the consensus. It should also improve the time between setting
+      up a bridge and seeing use by bridge users.
+    - Directory authorities no longer launch a TLS connection to every
+      relay as they startup. Now that we have 2k+ descriptors cached,
+      the resulting network hiccup is becoming a burden. Besides,
+      authorities already avoid voting about Running for the first half
+      hour of their uptime.
+
+
 Changes in version 0.2.2.12-alpha - 2010-04-20
   Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
   handle and vote on descriptors. It was causing relays to drop out of
diff --git a/changes/close_begindir_circs b/changes/close_begindir_circs
deleted file mode 100644
index 3b1ee87..0000000
--- a/changes/close_begindir_circs
+++ /dev/null
@@ -1,7 +0,0 @@
-  o Major bugfixes:
-    - Relays now close idle circuits early if it looks like they were
-      intended for directory fetches. Such circuits are unlikely to
-      be re-used, and tens of thousands of them were piling up at the
-      fast relays, causing the relays to run out of sockets and memory.
-      Bugfix on 0.2.0.22-rc (where clients started tunneling their
-      directory fetches over TLS).
diff --git a/changes/close_idle_conns_faster b/changes/close_idle_conns_faster
deleted file mode 100644
index 9eff607..0000000
--- a/changes/close_idle_conns_faster
+++ /dev/null
@@ -1,6 +0,0 @@
-  o Major bugfixes:
-    - Make relays more aggressive about closing TLS connections that
-      have no circuits on them. Tens of thousands of them were piling
-      up at the fast relays, causing the relays to run out of sockets
-      and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
-      their directory fetches over TLS).
diff --git a/changes/immediate_reachability_check b/changes/immediate_reachability_check
deleted file mode 100644
index 0352356..0000000
--- a/changes/immediate_reachability_check
+++ /dev/null
@@ -1,7 +0,0 @@
-  o Minor features:
-    - Directory authorities now do an immediate reachability check as soon
-      as they hear about a new relay. This change should slightly reduce
-      the time between setting up a relay and getting listed as running
-      in the consensus. It should also improve the time between setting
-      up a bridge and seeing use by bridge users.
-
diff --git a/changes/kill_clique_mode b/changes/kill_clique_mode
deleted file mode 100644
index 82283a8..0000000
--- a/changes/kill_clique_mode
+++ /dev/null
@@ -1,4 +0,0 @@
-  o Minor features:
-    - Finally get rid of the deprecated and now harmful notion of
-      "clique mode", where directory authorities maintain TLS connections
-      to every other relay.
diff --git a/changes/no_reachability_test_on_startup b/changes/no_reachability_test_on_startup
deleted file mode 100644
index e6a57a0..0000000
--- a/changes/no_reachability_test_on_startup
+++ /dev/null
@@ -1,6 +0,0 @@
-  o Minor features:
-    - Directory authorities no longer launch a TLS connection to every
-      relay as they startup. Now that we have 2k+ descriptors cached,
-      the resulting network hiccup is becoming a burden. Besides,
-      authorities already avoid voting about Running for the first half
-      hour of their uptime.
-- 
1.6.5