metasploit-version 0.1.2 → 0.1.3

data/features/metasploit-version/install/namespace_spec/gem_version_constant.feature

@@ -0,0 +1,154 @@
+Feature: metasploit-version install's <namespace>_spec.rb uses 'Metasploit::Version GEM_VERSION constant' shared example
+
+  The <namespace>_spec.rb will check that GEM_VERSION is defined correctly using the
+  'Metasploit::Version GEM_VERSION constant' shared example.
+
+  Background:
+    Given I successfully run `bundle gem namespace_spec`
+    And I cd to "namespace_spec"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem namespace_spec"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+    And I successfully run `metasploit-version install --force --no-bundle-install`
+    And I successfully run `git add *`
+    And I successfully run `git commit --all --message "metasploit-version install"`
+    And I successfully run `git checkout -b feature/MSP-1337/super-cool`
+
+  Scenario: GEM_VERSION is not defined
+    Given I overwrite "lib/namespace_spec/version.rb" with:
+      """
+      module NamespaceSpec
+        module Version
+          #
+          # CONSTANTS
+          #
+
+          # The major version number.
+          MAJOR = 0
+          # The minor version number, scoped to the {MAJOR} version number.
+          MINOR = 0
+          # The patch version number, scoped to the {MAJOR} and {MINOR} version numbers.
+          PATCH = 1
+          # The prerelease version, scoped to the {MAJOR}, {MINOR}, and {PATCH} version numbers.
+          PRERELEASE = 'super-cool'
+
+          #
+          # Module Methods
+          #
+          
+          # The full version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://semver.org/spec/v2.0.0.html semantic versioning v2.0.0} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}' on master.
+          #   '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}-PRERELEASE'
+          #   on any branch other than master.
+          def self.full
+            version = "#{MAJOR}.#{MINOR}.#{PATCH}"
+
+            if defined? PRERELEASE
+              version = "#{version}-#{PRERELEASE}"
+            end
+
+            version
+          end
+
+          # The full gem version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://guides.rubygems.org/specification-reference/#version RubyGems versioning} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}'
+          #   on master.  '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}.PRERELEASE'
+          #   on any branch other than master.
+          def self.gem
+            full.gsub('-', '.pre.')
+          end
+        end
+
+        # (see Version.full)
+        VERSION = Version.full
+      end
+      """
+    When I run `rake spec`
+    Then the exit status should not be 0
+    And the output should contain:
+      """
+             expected NamespaceSpec::GEM_VERSION to be defined
+      """
+    # On MRI and JRuby, the error is "uninitialized constant NamespaceSpace::GEM_VERSION", but on Rubinius the error is
+    # "Missing or uninitialized constant: NamespaceSpec::GEM_VERSION", so have to use match
+    And the output should match /uninitialized constant.*NamespaceSpec::GEM_VERSION/
+    And the output should contain " 2 failures"
+
+  Scenario: GEM_VERSION is not equal to Version.gem
+    Given I overwrite "lib/namespace_spec/version.rb" with:
+      """
+      module NamespaceSpec
+        module Version
+          #
+          # CONSTANTS
+          #
+
+          # The major version number.
+          MAJOR = 0
+          # The minor version number, scoped to the {MAJOR} version number.
+          MINOR = 0
+          # The patch version number, scoped to the {MAJOR} and {MINOR} version numbers.
+          PATCH = 1
+          # The prerelease version, scoped to the {MAJOR}, {MINOR}, and {PATCH} version numbers.
+          PRERELEASE = 'super-cool'
+
+          #
+          # Module Methods
+          #
+
+          # The full version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://semver.org/spec/v2.0.0.html semantic versioning v2.0.0} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}' on master.
+          #   '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}-PRERELEASE'
+          #   on any branch other than master.
+          def self.full
+            version = "#{MAJOR}.#{MINOR}.#{PATCH}"
+
+            if defined? PRERELEASE
+              version = "#{version}-#{PRERELEASE}"
+            end
+
+            version
+          end
+
+          # The full gem version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://guides.rubygems.org/specification-reference/#version RubyGems versioning} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}'
+          #   on master.  '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}.PRERELEASE'
+          #   on any branch other than master.
+          def self.gem
+            full.gsub('-', '.pre.')
+          end
+        end
+
+        # (see Version.full)
+        GEM_VERSION = Version.full
+
+        # (see Version.full)
+        VERSION = Version.full
+      end
+      """
+    When I run `rake spec`
+    Then the exit status should not be 0
+    And the output should contain:
+      """
+             expected NamespaceSpec::GEM_VERSION to equal NamespaceSpec::Version.gem
+      """
+    And the output should contain " 1 failure"

data/features/metasploit-version/install/namespace_spec/namespace.feature

@@ -0,0 +1,33 @@
+Feature: metasploit-version install's <namespace>_spec.rb generates proper namespace for gem name
+
+  The <namespace>_spec.rb that checks that GEM_VERSION and VERSION are defined correctly will use the fully-qualified
+  name for the gem namespace with proper conversion of underscored and dashes in the gem name to camel case and separate
+  modules, respectively.
+
+  Scenario Outline:
+    Given I successfully run `bundle gem <gem_name>`
+    And I cd to "<gem_name>"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem <gem_name>"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+    When I successfully run `metasploit-version install --force --no-bundle-install`
+    Then the file "<namespace_spec_rb_path>" should contain exactly:
+      """
+      RSpec.describe <gem_namespace_module> do
+        it_should_behave_like 'Metasploit::Version GEM_VERSION constant'
+        it_should_behave_like 'Metasploit::Version VERSION constant'
+      end
+
+      """
+
+    Examples:
+      | gem_name             | namespace_spec_rb_path                | gem_namespace_module |
+      | single               | spec/lib/single_spec.rb               | Single               |
+      | two_words            | spec/lib/two_words_spec.rb            | TwoWords             |
+      | parent-child         | spec/lib/parent/child_spec.rb         | Parent::Child        |
+      | two_words-child      | spec/lib/two_words/child_spec.rb      | TwoWords::Child      |
+      | parent-two_words     | spec/lib/parent/two_words_spec.rb     | Parent::TwoWords     |
+      | two_words-more_words | spec/lib/two_words/more_words_spec.rb | TwoWords::MoreWords  |

data/features/metasploit-version/install/namespace_spec/version_constant.feature

@@ -0,0 +1,179 @@
+Feature: metasploit-version install's <namespace>_spec.rb uses 'Metasploit::Version VERSION constant' shared example
+
+  The <namespace>_spec.rb will check that VERSION is defined correctly using the 'Metasploit::Version VERSION constant'
+  shared example.
+
+  Background:
+    Given I successfully run `bundle gem namespace_spec`
+    And I cd to "namespace_spec"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem namespace_spec"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+    And I successfully run `metasploit-version install --force --no-bundle-install`
+    And I successfully run `git add *`
+    And I successfully run `git commit --all --message "metasploit-version install"`
+    And I successfully run `git checkout -b feature/MSP-1337/super-cool`
+
+  Scenario: VERSION is not defined
+    # Have to ensure that gemspec doesn't reference the undefined NamespaceSpec::VERSION or rake spec won't even run
+    # due to NameError when gemspec is loaded by bundler.
+    Given I overwrite "namespace_spec.gemspec" with:
+      """
+      # coding: utf-8
+
+      Gem::Specification.new do |spec|
+        spec.name          = "add_development_dependency"
+        spec.version       = '0.0.0'
+        spec.authors       = ["Luke Imhoff"]
+        spec.email         = ["luke_imhoff@rapid7.com"]
+        spec.summary       = %q{TODO: Write a short summary. Required.}
+        spec.description   = %q{TODO: Write a longer description. Optional.}
+        spec.homepage      = ""
+        spec.license       = "MIT"
+
+        spec.files         = `git ls-files -z`.split("\x0")
+        spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+        spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+        spec.require_paths = ["lib"]
+
+        spec.add_development_dependency "bundler", "~> 1.6"
+        spec.add_development_dependency 'metasploit-version'
+        spec.add_development_dependency "rake"
+      end
+      """
+    And I overwrite "lib/namespace_spec/version.rb" with:
+      """
+      module NamespaceSpec
+        module Version
+          #
+          # CONSTANTS
+          #
+
+          # The major version number.
+          MAJOR = 0
+          # The minor version number, scoped to the {MAJOR} version number.
+          MINOR = 0
+          # The patch version number, scoped to the {MAJOR} and {MINOR} version numbers.
+          PATCH = 1
+          # The prerelease version, scoped to the {MAJOR}, {MINOR}, and {PATCH} version numbers.
+          PRERELEASE = 'super-cool'
+
+          #
+          # Module Methods
+          #
+          
+          # The full version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://semver.org/spec/v2.0.0.html semantic versioning v2.0.0} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}' on master.
+          #   '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}-PRERELEASE'
+          #   on any branch other than master.
+          def self.full
+            version = "#{MAJOR}.#{MINOR}.#{PATCH}"
+
+            if defined? PRERELEASE
+              version = "#{version}-#{PRERELEASE}"
+            end
+
+            version
+          end
+
+          # The full gem version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://guides.rubygems.org/specification-reference/#version RubyGems versioning} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}'
+          #   on master.  '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}.PRERELEASE'
+          #   on any branch other than master.
+          def self.gem
+            full.gsub('-', '.pre.')
+          end
+        end
+
+        # (see Version.gem)
+        GEM_VERSION = Version.gem
+      end
+      """
+    When I run `rake spec`
+    Then the exit status should not be 0
+    And the output should contain:
+      """
+             expected NamespaceSpec::VERSION to be defined
+      """
+    # On MRI and JRuby, the error is "uninitialized constant NamespaceSpace::VERSION", but on Rubinius the error is
+    # "Missing or uninitialized constant: NamespaceSpec::VERSION", so have to use match
+    And the output should match /uninitialized constant.*NamespaceSpec::VERSION/
+    And the output should contain " 2 failures"
+
+  Scenario: VERSION is not equal to Version.full
+    Given I overwrite "lib/namespace_spec/version.rb" with:
+      """
+      module NamespaceSpec
+        module Version
+          #
+          # CONSTANTS
+          #
+
+          # The major version number.
+          MAJOR = 0
+          # The minor version number, scoped to the {MAJOR} version number.
+          MINOR = 0
+          # The patch version number, scoped to the {MAJOR} and {MINOR} version numbers.
+          PATCH = 1
+          # The prerelease version, scoped to the {MAJOR}, {MINOR}, and {PATCH} version numbers.
+          PRERELEASE = 'super-cool'
+
+          #
+          # Module Methods
+          #
+
+          # The full version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://semver.org/spec/v2.0.0.html semantic versioning v2.0.0} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}' on master.
+          #   '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}-PRERELEASE'
+          #   on any branch other than master.
+          def self.full
+            version = "#{MAJOR}.#{MINOR}.#{PATCH}"
+
+            if defined? PRERELEASE
+              version = "#{version}-#{PRERELEASE}"
+            end
+
+            version
+          end
+
+          # The full gem version string, including the {NamespaceSpec::Version::MAJOR},
+          # {NamespaceSpec::Version::MINOR}, {NamespaceSpec::Version::PATCH}, and optionally, the
+          # `NamespaceSpec::Version::PRERELEASE` in the
+          # {http://guides.rubygems.org/specification-reference/#version RubyGems versioning} format.
+          #
+          # @return [String] '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}'
+          #   on master.  '{NamespaceSpec::Version::MAJOR}.{NamespaceSpec::Version::MINOR}.{NamespaceSpec::Version::PATCH}.PRERELEASE'
+          #   on any branch other than master.
+          def self.gem
+            full.gsub('-', '.pre.')
+          end
+        end
+
+        # (see Version.gem)
+        GEM_VERSION = Version.gem
+
+        VERSION = '1.2.3'
+      end
+      """
+    When I run `rake spec`
+    Then the exit status should not be 0
+    And the output should contain:
+      """
+             expected NamespaceSpec::VERSION to equal NamespaceSpec::Version.full
+      """
+    And the output should contain " 1 failure"

data/features/metasploit-version/install/rake_spec.feature

@@ -0,0 +1,27 @@
+Feature: metasploit-version install will setup rspec and rake spec
+
+  metasploit-version will call setup `spec/spec_helper.rb` and the `Rakefile` so that the user can run `rake spec` after
+  `metasploit-version install` completes
+
+  Background:
+    Given I successfully run `bundle gem specced`
+    And I cd to "specced"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem specced"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+    And I successfully run `metasploit-version install --force --no-bundle-install`
+
+  Scenario: spec is a listed task
+    When I run `rake -T`
+    Then the output should contain "rake spec"
+
+  Scenario: `rake spec` runs without error
+    When I successfully run `rake spec`
+    Then the output should contain "0 failures"
+
+  Scenario: `rake` runs `rake spec` by default
+    When I successfully run `rake`
+    Then the output should contain "0 failures"

data/features/metasploit-version/install/releasing/ruby_versions.feature

@@ -0,0 +1,50 @@
+Feature: metasplopit install should add RELEASING.md that handles multiple ruby versions
+
+  `metasploit-version` install should default to release instructions for MRI `ruby` and `jruby` with the ability to
+  override this default.
+
+  Background:
+    Given I successfully run `bundle gem released`
+    And I cd to "released"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem released"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+
+  Scenario: Default ruby versions
+    When I successfully run `metasploit-version install --force --no-bundle-install`
+    Then the file "RELEASING.md" should contain:
+      """
+
+      ## jruby
+      - [ ] `rvm use jruby@released`
+      - [ ] `rm Gemfile.lock`
+      - [ ] `bundle install`
+      - [ ] `rake release`
+
+      ## ruby-2.1
+      - [ ] `rvm use ruby-2.1@released`
+      - [ ] `rm Gemfile.lock`
+      - [ ] `bundle install`
+      - [ ] `rake release`
+      ```
+
+      ### Downstream dependencies
+      """
+
+  Scenario: Overridden ruby versions
+    When I successfully run `metasploit-version install --force --no-bundle-install --ruby-versions maglev`
+    Then the file "RELEASING.md" should contain:
+      """
+
+      ## maglev
+      - [ ] `rvm use maglev@released`
+      - [ ] `rm Gemfile.lock`
+      - [ ] `bundle install`
+      - [ ] `rake release`
+      ```
+
+      ### Downstream dependencies
+      """

data/features/metasploit-version/install/releasing/versioning.feature

@@ -0,0 +1,138 @@
+Feature: metasploit-version install should add RELEASING.md that handles pre-1.0.0 and post-1.0.0 versioning
+
+  `metasploit-version install` should have different directions for update the semantic version when it is < 1.0.0 and
+  >= 1.0.0.  These instructions should be based on the contents of CHANGELOG.md.
+
+  Background:
+    Given I successfully run `bundle gem released`
+    And I cd to "released"
+    And my git identity is configured
+    And I successfully run `git commit --message "bundle gem released"`
+    And I unset the environment variable "TRAVIS_BRANCH"
+    And I set the environment variables to:
+      | variable            | value |
+      | TRAVIS_PULL_REQUEST | false |
+
+  Scenario: < 1.0.0
+    When I successfully run `metasploit-version install --force --major 0 --minor 1 --patch 2 --no-bundle-install`
+    Then the file "RELEASING.md" should contain:
+      """
+      ### Compatible changes
+
+      If the [CHANGELOG.md](CHANGELOG.md) contains only Enhancements, Bug Fixes, and/or Deprecations for the Next Release then
+      increment [`PATCH`](lib/released/version.rb).
+
+      ### Incompatible changes
+
+      If the [CHANGELOG.md](CHANGELOG.md) contains any Incompatible Changes for the Next Release, then you can either (1)
+      decide to remain pre-1.0.0 or (2) advance to 1.0.0.
+
+      1. To remain pre-1..0.0, then increment [`MINOR`](lib/released/version.rb) and reset [`PATCH`](lib/released/version.rb) to `0`.
+      2. To advance to 1.0.0, increment [`MAJOR`](lib/released/version.rb) and reset [`MINOR`](lib/released/version.rb and [`PATCH`](lib/released/version.rb) to `0`.
+
+      """
+
+  Scenario: 1.0.0
+    When I successfully run `metasploit-version install --force --major 1 --minor 0 --patch 0 --no-bundle-install`
+    Then the file "RELEASING.md" should contain:
+      """
+      ### Bug fixes
+
+      If the [CHANGELOG.md](CHANGELOG.md) contains only Bug Fixes for the Next Release, then increment
+      [`PATCH`](lib/released/version.rb).
+
+      ### Compatible API changes
+
+      If the [CHANGELOG.md](CHANGELOG.md) contains any Enhancements or Deprecations, then increment
+      [`MINOR`](lib/released/version.rb) and reset [`PATCH`](lib/released/version.rb) to `0`.
+
+      ### Incompatible API changes
+
+      If the [CHANGELOG.md](CHANGELOG.md) contains any Incompatible Change, then increment [`MAJOR`](lib/released/version.rb) and
+      reset [`MINOR`](lib/released/version.rb and [`PATCH`](lib/released/version.rb) to `0`.
+
+      """
+
+  Scenario: Version indepedent
+    When I successfully run `metasploit-version install --force --major 0 --minor 1 --patch 2 --no-bundle-install`
+    Then the file "RELEASING.md" should contain:
+      """
+      # Releasing
+
+      These steps can be added to the Pull Request description's task list to remind the reviewer of how to release the
+      gem.
+
+      ```
+      # Release
+
+      Complete these steps on DESTINATION
+
+      ## [CHANGELOG.md](CHANGELOG.md)
+
+      ### Terminology
+
+      * "Enhancements" are widdening the API, such as by adding new classes or methods.
+      * "Bug Fixes" are fixes to the implementation that do not affect the public API.  If the public API is affected then
+        the change should be listed as both a "Bug Fix" and either an "Enhancement" or "Incompatible Change" depending on how
+        the bug was fixed.
+      * "Deprecations" are changes to the implementation that cause deprecation warnings to be issued for APIs which will be
+        removed in a future major release.  "Deprecations" are usually accompanied by an Enhancement that creates a new API
+        that is meant to be used in favor of the deprecated API.
+      * "Incompatbile Changes" are the removal of classes or methods or new required arguments or setup that shrink the API.
+        It is best practice to make a "Deprecation" for the API prior to its removal.
+
+      ### Task List
+
+      - [ ] Generate the list of changes since the last release: `git log v<LAST_MAJOR>.<LAST_MINOR>.<LAST_PATCH>..HEAD`
+      - [ ] For each commit in the release, find the corresponding PR by search for the commit on Github.
+      - [ ] For each PR, determine whether it is an Enhancement, Bug Fix, Deprecation, and/or Incompatible Change.  A PR can
+            be in more than one category, in which case it should be listed in each category it belongs, but with a category
+            specific description of the change.
+      - [ ] Add an item to each category's list in the following format: `[#<PR>](https://github.com/rapid7/released/pull/<PR>) <consumer summary> - [@<github_user>](https://github.com/<github_user>)`
+            `consumer_summary` should be a summary of the Enhancement, Bug Fix, Deprecation, or Incompatible Change from a
+            downstream consumer's of the library's perspective.  `github_user` should be Github handle of the author of the
+            PR.
+      - [ ] If you added any Deprecations or Incompatible Changes, then adding upgrading information to
+            [UPGRADING.md](UPGRADING.md)
+
+      ## `VERSION`
+
+      The entries in the [CHANGELOG.md](CHANGELOG.md) can be used to help determine how the `VERSION` should be bumped.
+
+      """
+    And the file "RELEASING.md" should contain:
+      """
+
+      ## Setup [CHANGELOG.md](CHANGELOG.md) for next release
+
+      - [ ] Change `Next Release` section name at the top of [CHANGELOG.md](CHANGELOG.md) to match the current `VERSION`.
+      - [ ] Add a new `Next Release` section above the `VERSION`'s section you just renamed:
+      <pre>
+      # Next Release
+
+      * Enhancements
+      * Bug Fixes
+      * Deprecations
+      * Incompatible Changes
+      </pre>
+
+      ## Release to rubygems.org
+
+      ## jruby
+      - [ ] `rvm use jruby@released`
+      - [ ] `rm Gemfile.lock`
+      - [ ] `bundle install`
+      - [ ] `rake release`
+
+      ## ruby-2.1
+      - [ ] `rvm use ruby-2.1@released`
+      - [ ] `rm Gemfile.lock`
+      - [ ] `bundle install`
+      - [ ] `rake release`
+      ```
+
+      ### Downstream dependencies
+
+      There are currently no known downstream dependenci
+      """
+