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: = Versioning
  
  NOTE: Some of the information here is forward looking, as RuboCop 1.0 is still not released.
  
  RuboCop is stable between major versions, both in terms of API and cop
  configuration.
  
  == Release Policy
  
  We're following https://semver.org/[Semantic Versioning] (as much as
  one can be following it when the major version is 0). At this point
  bumps of the minor (second) version number are considered major releases
  and always include new features or significant changes to existing
  features. 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 major
  release starts immediately after the previous one has been
  shipped. Bugfix/point releases (if any) address only serious bugs and
  never contain new features.
  
  Here are a few examples:
  
  * 0.50.0 - Feature release
  * 0.50.1 - Bug-fix release
  * 0.50.2 - Bug-fix release
  * 0.51.0 - Feature release
  
  == Pending Cops
  
  
negative.code:   Enabled: false
  ----
  
  IMPORTANT: On major RuboCop version updates (e.g. 1.0 -> 2.0), *all* pending cops are enabled in bulk.
  