Updating upgrade guide.

Alexandre Dutra · Alexandre Dutra · commit 7e3b38f5f3ce · 2015-10-05T17:48:34.000+02:00
diff --git a/upgrade_guide/README.md b/upgrade_guide/README.md
@@ -36,21 +36,18 @@ binary compatibility.
     If this is a problem for you, `MappingManager(Session, ProtocolVersion)`
     preserves the previous behavior (see the API docs for more details).
 
-Merged from 2.0.11:
-
-4. The `DefaultRetryPolicy`'s behaviour has changed in the case of an Unavailable
-   exception received from a request. The new behaviour will cause the driver to
-   process a Retry on a different node at most once, otherwise an exception will
-   be thrown. This change makes sense in the case where the node tried initially
-   for the request happens to be isolated from the rest of the cluster (e.g.
-   because of a network partition) but can still answer to the client normally.
-   In this case, trying another node has a chance of success.
-   The previous behaviour was to always throw an exception.
-5. A `BuiltStatement` is now considered non-idempotent whenever a `fcall()`
+4. A `BuiltStatement` is now considered non-idempotent whenever a `fcall()`
    or `raw()` is used to build a value to be inserted in the database.
    If you know that the CQL functions or expressions are safe, use
    `setIdempotent(true)` on the statement.
 
+5. The list of contact points provided at startup is now shuffled before trying
+   to open the control connection, so that multiple clients with the same contact
+   points don't all pick the same control host. As a result, you can't assume that
+   the driver will try contact points in a deterministic order. In particular, if
+   you use the `DCAwareRoundRobinPolicy` without specifying a primary datacenter
+   name, make sure that you only provide local hosts as contact points.
+
 
 ### 2.1.6
 
