anchor.diff:  
   See: link:https://issues.apache.org/jira/browse/TINKERPOP-2476[TINKERPOP-2476]
   
  -==== Anonymous Child Traversals
  -
  -TinkerPop conventions for child traversals is to spawn them anonymously from `__`, therefore:
  -
  -[source,groovy]
  -g.addV('person').addE('self').to(__.V(1))
  -
  -or more succinctly via static import as:
  -
  -[source,groovy]
  -g.addV('person').addE('self').to(V(1))
  -
  -Some users have chosen to instead write the above as:
  -
  -[source,groovy]
  -g.addV('person').addE('self').to(g.V(1))
  -
  -which spawns a child traversal from a `GraphTraversalSource`. When spawned this way, a traversal is bound to a "source"
  -and therefore is not anonymous. While the above code worked, it is important that there be less ways to do things
  -with Gremlin so as to avoid confusion in examples, documentations and mailing list answers.
  -
  -As of 3.5.0, attempting to use a traversal spawned from a "source" will result in an exception. Users will need to
  -modify their code if they use the unconventional syntax.
  -
  -See: link:https://issues.apache.org/jira/browse/TINKERPOP-2361[TINKERPOP-2361]
  -
  -[[graphson-and-jsonbuilder]]
  -==== GraphSON and JsonBuilder
  +[[serialization-3_5_0]]
  +==== Serialization
  +
  +*Java and Gryo*
  +
  +Since the first release of TinkerPop 3.x, Gryo has been the default serialization format for Gremlin Server and
  +Java Driver. It was also used as the default serialization format for Gremlin Console remote connectivity to Gremlin
  +Server. As of this release, Gryo has been replaced as the default by GraphBinary. All packaged configuration files
  +and programmatic defaults have been modified as such.
  +
  +It is still possible to utilize Gryo as a message serialization format by modifying Gremlin Server configuration files
  +to include the appropriate Gryo configurations. If using Gryo, do not user earlier versions of the driver and server
  +with 3.5.0. Use a 3.5.0 client to connect to a 3.5.0 server. Generally speaking, mixed version combinations will
  +appear to work properly, but problems will likely occur during general course of usage and it is therefore not
  +advisable to take this approach.
  +
  +For best compatibility between 3.4.x and 3.5.x, please use GraphBinary.
  +
  +*GraphSON and JsonBuilder*
   
   GraphSON serialization support for Groovy's `JsonBuilder` has been present since the first version of GraphSON. That
   approach to returning results has never materialized as a standardized way to use Gremlin as originally envisioned.
  
positive.code: The `${groovy.version}` should match the version specified in TinkerPop's root
  link:https://github.com/apache/tinkerpop/blob/master/pom.xml[pom.xml].
  
  See: link:https://issues.apache.org/jira/browse/TINKERPOP-2460[TINKERPOP-2460]
  
  ==== Gryo Usage
  
  Since the first release of TinkerPop 3.x, Gryo has been the default serialization format for Gremlin Server and
  Java Driver. It was also used as the default serialization format for Gremlin Console remote connectivity to Gremlin
  Server. As of this release, Gryo has been replaced as the default by GraphBinary. All packaged configuration files
  and programmatic defaults have been modified as such.
  
  It is still possible to utilize Gryo as a message serialization format by modifying Gremlin Server configuration files
  to include the appropriate Gryo configurations. If using Gryo, do not user earlier versions of the driver and server
  with 3.5.0. Use a 3.5.0 client to connect to a 3.5.0 server. Generally speaking, mixed version combinations will
  appear to work properly, but problems will likely occur during general course of usage and it is therefore not
  advisable to take this approach.
  
  For best compatibility between 3.4.x and 3.5.x, please use GraphBinary.
  
  See: link:https://issues.apache.org/jira/browse/TINKERPOP-2259[TINKERPOP-2259]
  
  ==== Use of null
  
  
negative.code: 
  The `gremlin-driver` module made its dependency on Groovy `optional` as its only reason for inclusion was to support
  `JsonBuilder` serialization and this feature is little known and perhaps even less used. Read more about this change
  here in the Upgrade Documentation in the <<serialization-3_5_0, Serialization Section>> under the subsection title
  "GraphSON and JsonBuilder".
  
  See: link:https://issues.apache.org/jira/browse/TINKERPOP-2185[TINKERPOP-2185]
  
  