--- AnyEvent/Changes	2011/08/02 22:30:00	1.454
+++ AnyEvent/Changes	2011/08/04 09:14:01	1.455
@@ -5,13 +5,19 @@
 TODO: anyevent::trace? or debug tracing all watchers?
 TODO: anyevent strict checking for $_ changes?
 
-TODO: Kevin Ryde         (3.8K)   1 inbox       Glib child processes
 	- INCOMPATIBLE CHANGE: AnyEvent::DNS resource records now include
           the TTL as fourth element - this affects ->resolve directly,
           and ->request and ->dns_unpack indirectly. Convenience functions
           such as AnyEvent::DNS::{a,txt,mx,srv} are not affected.
         - INCOMPATIBLE CHANGE: backend authors now should not implement
-          one_event or loop, but instead the AnyEvent::CondVar::_wait method.
+          one_event or loop, but instead the AnyEvent::CondVar::_wait and _poll
+          methods.
+        - DEPRECIATION: please change
+          "use AnyEvent::Impl::Perl" to "use AnyEvent::Loop" and
+          "AnyEvent::Impl::Perl::loop" to "AnyEvent::Loop::run"
+          in your programs, for future compatibility.
+        - split the pure perl backend into a loop module and an impl
+          module (AnyEvent::Loop and AnyEvent::Impl::Perl).
         - some read types (regex, netstring, json, storable) could
           errornously keep an AE::Handle object alive on their own
           (reported by Mohammad Toossi).