--- AnyEvent/Changes	2014/12/26 21:55:01	1.597
+++ AnyEvent/Changes	2017/06/10 16:38:19	1.623
@@ -8,10 +8,78 @@
 TODO: AnyEvent::Handle with AnyEvent::IO?
 TODO: invalid. and localhost. specialcasing inside AEDNS and not AESocket (rfc6761)
 TODO: maybe implement env variable to give hosts precedence
+TODO: more formats for parse_ipv6 (single ipv6 address without port, ...p80, ...#80)
+TODO: inet_aton maybe pack C4? no, add a comment why not
 
+TODO: socket prepare callbacks, can they easily signal failure as well?
+7.14
+	- fix a crash bug in AnyEvent::Handle with openssl 1.1.0 (patched
+	  by Paul Howarth and apparently tracked down by Mike McCauley).
+	- AnyEvent::Handle->keepalive was documented (and defined) twice
+          (found by Matt Merhar).
+        - AnyEvent::Socket::tcp_bind/tcp_server would immediately unlink a unix
+          listening socket unless a guard is used. Change this so that no
+          cleanup will be performed unless a guard is used and document this more
+          clearly.
+        - make tcp_bind/tcp_server error messages more regular.
+        - work around latest perl upstream breakage - this time, perl5porters were
+          apparently bullied by a bogus CVE (CVE-2016-1238), and since distros
+          stupidly apply anything that has "security fix" stamped on it, it's likely
+          going to be a problem in practise (and working around it is trivial on
+          windows and unix).
+        - add TCP_FASTOPEN/MSG_FASTOPEN and MSG_NOSIGNAL/MSG_MORE/MSG_DONTWAIT
+          to constants.
+        - update warnings to common::sense 3.74 standards.
+
+7.13 Sat Sep 17 04:31:49 CEST 2016
+	- Only call tlsext_host_name for non-empty common names (reported
+          by Maxime Soulé).
+        - log a (single) notice message if SNI is not supported.
+        - upgrade to UTS-46:9.0.0 draft and switch to non-transitional
+          behaviour, beating thunderbird, ie, edge, chrome and safari to it :)
+          (see also https://bugzilla.mozilla.org/show_bug.cgi?id=1218179)
+        - turns out the UTS-46 IDNA testcase failures were indeed bugs in the
+          testcases and the specification and not in the code - the post-9.0.0
+          unicode files have all known problems fixed, so finally the AnyEvent
+          IDNA implementation can pass the full IDNA testsuite - without needing
+          a single fix :)
+        - guarantee (and document) that condvar callbacks will be removed
+          on invocation - important to avoid circular references.
+
+7.12 Wed Jan 27 19:12:26 CET 2016
+	- use common name as hostname for tls connects, if Net::SSLeay
+          supports SNI.
+        - fix documentation of tls_autostart read type in AnyEvent::Handle,
+          analyzed by Felix Ostmann.
+
+7.11 Thu Jul 16 14:36:00 CEST 2015
+	- AnyEvent::Socket::parse_ipv6 could accept malformed ipv6
+          addresses (extra "::" at end and similar cases).
+	- add a more explicit warning to AnyEvent::Handle that it doesn't
+          work on files, people keep getting confused.
+        - new function AnyEvent::Socket::tcp_bind.
+        - new functions AnyEvent::fh_block and AnyEvent::fh_unblock.
+	- aligned ipv6 address formatting with RFC 5952 (by not shortening
+          a single :0: to ::).
+        - added stability canary support.
+
+7.09 Sat May  2 16:38:53 CEST 2015
 	- AnyEvent::Debug called an internal function (AnyEvent::Log::ft)
           that was renamed to AnyEvent::Log:format_time. uinder its old name
           (analyzed by Michael Stovenour).
+        - update AnyEvent::DNS fallback resolver addresses:
+          seems google effectively killed most other free dns resolvers,
+          so remove them, but add cable and wireless (ecrc) since it was
+          stable for 20 years or so, official or not, and there should be
+          an alternative to google.
+        - perl5porters broke windows error codes in 5.20, and mapped
+          WSAEWOULDBLOCK on the (different) EWOULDBLOCK error code, and
+          WSAEINPROGRESS into the incompatible ERINPROGRESS code, probably
+          because they were so cool. They probably broke other error codes
+          for no reason, too, but I didn't care for checking, it's too
+          depressing. This version only works around the WSAEWOULDBLOCK
+          issue, because I don't have a nice way to work around the
+          WSAEINPROGRESS bug.
 
 7.08 Wed Dec 10 05:27:17 CET 2014
         - work around a newly introduced bug in Socket 2.011 (an