anchor.diff:  - `CamelContextRoutesStopping` to `RoutesStopping`
   - `CamelContextRoutesStopped` to `RoutesStopped`
   
  -The method `isOnlyDynamicQueryParameters` is removed from `org.apache.camel.spi.SendDynamicAware` and
  +The method `isOnlyDynamicQueryParameters` was removed from `org.apache.camel.spi.SendDynamicAware` and
   `org.apache.camel.support.component.SendDynamicAwareSupport` classes.
   
  -The `PackageScanResourceResolver` has been revisited and `findResources`` now returns a colelctions of `org.apache.camel.spi.Resource` which provide both the location of the resolved resources an a method to open the related InpuStream:
  +The class `PackageScanResourceResolver` has been revisited and the method `findResources` now returns a collection of `org.apache.camel.spi.Resource`
  +which provide both the location of the resolved resources and a method to open the related `InpuStream`:
   
   [source,java]
   ----
  
positive.code: There are now two components for Infinispan:
  
  - *camel-infinispan* to integrate with remote caches through the Hot Rod protocol (scheme: *infinispan*).
  - *camel-infinispan-embedded* to integrate with local/embedded caches  (scheme: *infinispan-embedded*).
  
  As conseguence of the refactor
  
  - the remote and embedded endpoints provide support the same capabilities, as example queries were only possible on a remote cache and now they are suported on both remote and local/embedded caches
  - the configuration options for the endpoint are now specific to the context which remove the possibility to mix unrelated propertis
  
negative.code: 
  === OnCompletion EIP
  
  The `onCompletion` EIP has been fixed. It could trigger multiple completions for a given `Exchange` before.
  
  === Transactions and Multicast, Splitter, or Recipient List EIPs
  
  When using `transacted` in Camel routes with Multicast, Splitter, or Recipient List EIPs, the exection strackframe
  could grown deep and this could cause a stack overflow exception. This has been fixed by refactoring the EIP into a special
  transacted mode and the existing reactive mode.
  
  We do not anticipate any issues but if you are using transactions and these EIPs then we would like to have feedback
  