anchor.diff:  We're fully aware of this being not ideal, but we decided to still go this route as a first step,
   allowing us to get some experiences with Oracle and also get a connector into the hands of those with the required license handy.
   Going forward, we are going to explore alternative approaches.
  -We already have some ideas around this, so please stay tuned (the issue to track is https://issues.jboss.org/browse/DBZ-137[DBZ-137]).
  +We already have some ideas and discussions around this, so please stay tuned (the issue to track is https://issues.jboss.org/browse/DBZ-137[DBZ-137]).
   
   The Oracle connector is going to evolve within the next 0.8.x releases.
   To learn more about it, please check its link:/docs/connectors/oracle[connector documentation page].
  
positive.code: but over time it also revealed some shortcomings; as the DDL language is quite extensive,
  we saw repeatedly bug reports caused by some specific DDL constructs not being parseable.
  
  So we decided to go back to drawing board and came up with a brand new parser design.
  Thanks to the great work of Roman Kuchar, we now have a completely new DDL parser
  which is based on the proven and very mature http://antlr.org/[Antlr] parser generator
  (luckily, the Antlr project provides a complete MySQL grammar).
  
negative.code: 
  Due to the big number of changes (the release contains exactly https://issues.jboss.org/issues/?jql=project%20%3D%20DBZ%20AND%20fixVersion%20%3D%200.8.0.Beta1[42 issues] overall),
  we decided to alter our versioning schema a little bit:
  going forward we may do one or more Beta and CR ("candidate release") releases before doing a final one.
  This will allow us to get feedback from the community early on,
  while still completing and polishing specific features.
  Final (stable) releases will be named like 0.8.0.Final etc.
  