README.markdown in zk-1.2.0 vs README.markdown in zk-1.3.0

- old
+ new
@@ -61,9 +61,17 @@
 [EventMachine]: https://github.com/eventmachine/eventmachine
 [zk-eventmachine]: https://github.com/slyphon/zk-eventmachine
 
 ## NEWS ##
 
+### v1.3.0 ###
+
+Phusion Passenger and Unicorn users are encouraged to upgrade!
+
+* __fork()__: ZK should now work reliably after a fork() if you call `reopen()` ASAP in the child process (before continuing any ZK work). Additionally, your event-handler (blocks set up with `zk.register`) will still work in the child. You will have to make calls like `zk.stat(path, :watch => true)` to tell ZooKeeper to notify you of events (as the child will have a new session), but everything should work.
+
+* See the fork-handling documentation [on the wiki](http://github.com/slyphon/zk/wiki/Forking).
+
 ### v1.2.0 ###
 
 You are __STRONGLY ENCOURAGED__ to go and look at the [CHANGELOG](http://git.io/tPbNBw) from the zookeeper 1.0.0 release
 
 * NOTICE: This release uses the 1.0 release of the zookeeper gem, which has had a MAJOR REFACTORING of its namespaces. Included in that zookeeper release is a compatibility layer that should ease the transition, but any references to Zookeeper\* heirarchy should be changed. 