anchor.diff:  ==>[a:marko]
   ----
   
  -Above is the old behavior; the second `select("a")` has no effect, it selects the side-effect `a` again, although one would expect to get the map entry `a`. What follows is the new behavior:
  +Above is the old behavior; the second `select("a")` has no effect, it selects the side-effect `a` again, although one
  +would expect to get the map entry `a`. What follows is the new behavior:
   
   [source,groovy]
   ----
  
positive.code: 
  ==== Changed Infix Behavior
  
  The infix notation of `and()` and `or()` now supports an arbitrary number of traversals and `ConnectiveStrategy` produces a traversal with proper AND and OR semantics.
  
  ```
  Input: a.or.b.and.c.or.d.and.e.or.f.and.g.and.h.or.i
  
negative.code: ==>[value:santa fe,startTime:2005]
  ```
  
  As shown above, the support of the `with()` modulator for `valueMap()` makes the `valueMap(boolean)` overload
  superfluous, hence this overload is now deprecated. This is a breaking API change, since `valueMap()` will now always
  yield instances of type `Map<Object, Object>`. Prior this change only the `valueMap(boolean)` overload yielded
  `Map<Object, Object>` objects, `valueMap()` without the boolean parameter used to yield instances of type
  `Map<String, Object>`.
  
  See: link:https://issues.apache.org/jira/browse/TINKERPOP-2059[TINKERPOP-2059]
  
  ==== Number Comparison of Predicates
  
  In previous versions `within()` and `without()` performed strict number comparisons; that means these predicates did
  not only compare number values, but also the type. This was inconsistent with how other predicates (like `eq, `gt`,
  etc.) work. All predicates will now ignore the number type and instead compare numbers only based on their value.
  
  Old behavior:
  
  