anchor.diff:    NewCops: enable
   ----
   
  -The following setting or using `rubocop --disable-pending-cops` command-line option, pending cops are disabled in bulk.
  +Alternatively, you can use following configuration or the `--disable-pending-cops` command-line option, to disable all pending cops in bulk:
   
   [source,yaml]
   ----
  
positive.code: You can see that 3 new cops were added in RuboCop 0.80 and it's up to you
  to decide if you want to enable or disable them.
  
  To suppress this message set `NewCops` to either `enable` or `disable` in your `.rubocop.yml` file.
  
  The following setting or using `rubocop --enable-pending-cops` command-line option, pending cops are enabled in bulk.
  
  [source,yaml]
  ----
  
negative.code: = Versioning
  
  RuboCop is stable between major versions, both in terms of API and cop
  configuration. We aim the ease the maintenance of RuboCop extensions
  (by keeping the API stable) and the upgrades between RuboCop releases
  (by not enabling new cops and changing the configuration of existing cops).
  All big (breaking) changes are reserved for major releases.
  
  == Release Policy
  
  We're following https://semver.org/[Semantic Versioning].  API
  compatibility between major releases is a big concern, as there are
  many RuboCop extensions that can be affected by breaking API changes.
  
  The development cycle for the next minor (feature) release starts
  immediately after the previous one has been shipped. Bug-fix (point)
  releases (if any) address only serious bugs and never contain new
  features.
  
  Here are a few examples:
  
  * 1.1.0 - Feature release
  * 1.1.1 - Bug-fix release
  * 1.1.2 - Bug-fix release
  * 1.2.0 - Feature release
  
  NOTE: Prior to RuboCop 1.0 bumps of the minor (second) version number
  were considered major releases and always included new features and/or
  changes to existing features.
  
  == Pending Cops
  
  