--- AnyEvent/Changes	2012/03/27 16:21:11	1.530
+++ AnyEvent/Changes	2012/03/29 04:13:32	1.534
@@ -3,8 +3,22 @@
 TODO: document TCP_*** constants
 TODO: add debug/trace logging to some modules
 TODO: AnyEvent::IO
+TODO: PERL_ANYEVENT_IO_MODEL docs
+tODO: maxim souffle handle storable
+TODO: document import tags aeio, also ae_ naming
+TODO: t/io
+lib/AnyEvent/DNS.pm:   open my $fh, "<", $resolv_conf
+lib/AnyEvent/DNS.pm:         if (open my $fh, "ipconfig /all |") {
+lib/AnyEvent/Log.pm:   open my $fh, ">>", $path
+lib/AnyEvent/Log.pm:      open my $fh, ">>", $path
+lib/AnyEvent/Socket.pm:   open my $fh, "<",
+lib/AnyEvent/TLS.pm:         or croak "$dh_file: failed to open DH parameter file: $!";
 
+6.2
 	- documented Rocco fabricating statements about AnyEvent and me.
+	- new module AnyEvent::IO, that is a frontend to either a pure-perl
+          synchronous I/O implementation (AnyEvent::IO::Perl), or to the
+          asynchronous I/O extension IO::AIO (AnyEvent::IO::IOAIO).
         - the default logging level was not properly documented in a variety of
           places, this has hopefully been rectified.
 	- updated uts46data.pl for unicode 6.1.0.
@@ -13,6 +27,8 @@
           by default already.
         - upgrade to the trick used by common-sense 3.5 to work
           around extra warning torture/breakage under perl 5.15.x.
+        - log messages by anyevent are now ucfirst, are usually full
+          sentences and do no longer include the package name.
 
 6.14 Tue Jan 31 20:00:24 CET 2012
 	- AnyEvent::Impl::Tk was broken due to a mysterious "die" inside,
@@ -112,7 +128,7 @@
         - env variables can now be specified using AE_xyz instead of
           PERL_ANYEVENT_xyz, subject to some rules.
         - lots of new AnyEvent::Debug functionality.
-        - AnyEvent::Strict now checks for modifications $_ by the callback
+        - AnyEvent::Strict now checks for modifications of $_ by the callback
           (by setting it to readonly while executing the callback, if possible).
         - IO::Async sometimes cancels the wrong timer when you call cancel_timer.
           Invest extra overhead to work around this peculiar behaviour.