anchor.diff:  [source, xml]
   ----
     <exhaustiveSearch>
  -<exhaustiveSearchType>BRUTE_FORCE</exhaustiveSearchType>
  +    <exhaustiveSearchType>BRUTE_FORCE</exhaustiveSearchType>
     </exhaustiveSearch>
   ----
   There is now a better alternative to Brute Force: Branch And Bound, see docs for more information.
  
positive.code: === `<entitySelector>`: `<cacheType>PHASE</cacheType>` obsolete
  
  If you explicitly configured all your `<entitySelector>` elements with `<cacheType>PHASE</cacheType>` for performance,
  you know no longer have to do that, as OptaPlanner does the fast thing out of the box,
  if and only if no other properties (such as filtering) were specified on that `<entitySelector>`.
  
  Before in `*SolverConfig.xml` and `*BenchmarkConfig.xml`:
  
negative.code:   <warmUpMinutesSpentLimit>...</warmUpMinutesSpentLimit>
    <warmUpHoursSpentLimit>...</warmUpHoursSpentLimit>
    ...
  </plannerBenchmark>
  ----
  
  [.upgrade-recipe-minor]
  