rubygems-update 2.6.3 → 2.7.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: bed7c7899639f9d4eb539d69521ede2590f48bf7
-  data.tar.gz: 8a477e9b22457409b503bfd6c2d4db1b210d4bd8
+SHA256:
+  metadata.gz: 8894c9873527e4af5cc83ac8aded3cee104bcc856ca20bb56fc1323b42505e12
+  data.tar.gz: 931f155a8de59dd9b17423356e1dc0de54f3cf5b40bbe5eae801c884420a9407
 SHA512:
-  metadata.gz: ab3c776e4e1f56437bcab1717d93b228519eb7a9b945868e91e8ec22e85f06b0201df7579c0450f8b45d3a0692e3abed75561d55dce83ec09e405d66a8ebcc03
-  data.tar.gz: ac178d28e4a95baf5ae57d1e8f90d0195b83b2b7591595a4a7415839dfc7d661cba75448916f036e300f1eb8b30b9cb53f2f3152cd2bc98dbda6de8db74a4419
+  metadata.gz: 2b23ba224604b357bb71d7f0aff9bb7e73979bb53c59310ef70566e8df2bbaca3c3aec46961cfdd38262baba89af52c8131a4d3eecc50470b2181c52b8db340d
+  data.tar.gz: e1632f7987dbd4eaa50704237ea7b78cb952ca6f775ed4613399c7b4797e0fb92402a1af7ea4f4cd39e38065c4883a4ba0acc07086ee908d0eb6e50ad356e497

data/.travis.yml

@@ -1,51 +1,34 @@
 ---
 after_script:
-- rake travis:after -t
+- util/ci after_script
 before_script:
-- gem uninstall executable-hooks gem-wrappers -x --force -i `gem env home`@global
-- gem install rake -v '~> 10.5' --no-document
-- gem install hoe-travis --no-document
-- gem install minitest -v '~> 4.7' --no-document
-- rake travis:before -t
-- gem list --details
-- gem env
+- util/ci before_script
 language: ruby
-notifications:
-  email:
-  - drbrain@segment7.net
-  - evan+notify@phx.io
+dist: trusty
+sudo: required
 branches:
   only:
     - master
     - auto
-    - /[\d.]+/
+    - /^[\d.]+$/
+    - /.+-stable$/
 rvm:
 - 1.8.7
 - 1.9.2
 - 1.9.3
 - 2.0.0
-- 2.1.7
-- 2.2.3
-- 2.3.0
+- 2.1.10
+- 2.2.9
+- 2.3.6
+- 2.4.3
+- 2.5.0
 - ruby-head
 env:
-  - "YAML=syck"
-  - "YAML=psych"
-script: rake travis
+  - "TEST_TOOL=rubygems YAML=syck"
+  - "TEST_TOOL=rubygems YAML=psych"
+  - "TEST_TOOL=bundler RGV=master"
+script:
+  - util/ci script
 matrix:
-  exclude:
-    - rvm: 1.8.7
-      env: "YAML=psych"
-    - rvm: 2.0.0
-      env: "YAML=syck"
-    - rvm: 2.1.7
-      env: "YAML=syck"
-    - rvm: 2.2.3
-      env: "YAML=syck"
-    - rvm: 2.3.0
-      env: "YAML=syck"
-    - rvm: ruby-head
-      env: "YAML=syck"
   allow_failures:
-    - rvm: ruby-head
-sudo: false
+    - env: "TEST_TOOL=bundler RGV=master"

data/CODE_OF_CONDUCT.md

@@ -1,40 +1,43 @@
 # Contributor Code of Conduct
 
-As contributors and maintainers of this project, and in the interest of
-fostering an open and welcoming community, we pledge to respect all people who
-contribute through reporting issues, posting feature requests, updating
-documentation, submitting pull requests or patches, and other activities.
+### Our Pledge
 
-We are committed to making participation in this project a harassment-free
-experience for everyone, regardless of level of experience, gender, gender
-identity and expression, sexual orientation, disability, personal appearance,
-body size, race, ethnicity, age, religion, or nationality.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing other's private information, such as physical or electronic
-  addresses, without explicit permission
-* Other unethical or unprofessional conduct.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct. By adopting this Code of Conduct,
-project maintainers commit themselves to fairly and consistently applying these
-principles to every aspect of managing this project. Project maintainers who do
-not follow or enforce the Code of Conduct may be permanently removed from the
-project team.
-
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by opening an issue or contacting one or more of the project
-maintainers.
-
-This Code of Conduct is adapted from the [Contributor
-Covenant](http://contributor-covenant.org), version 1.2.0, available at
-[http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the [project team](MAINTAINERS.txt). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4.

data/CONTRIBUTING.rdoc

@@ -1,7 +1,7 @@
 = How to contribute
 
-Community involvement is essential to RubyGems. We want to keep it easy as
-possible to contribute changes. There are a few guidelines that we need
+Community involvement is essential to RubyGems. We want to keep it as easy
+as possible to contribute changes. There are a few guidelines that we need
 contributors to follow to reduce the time it takes to get changes merged in.
 
 == Guidelines
@@ -11,11 +11,13 @@ contributors to follow to reduce the time it takes to get changes merged in.
 2. Ensure that your code blends well with ours:
    * No trailing whitespace
    * Match indentation (two spaces)
-   * Match coding style (`if`, `elsif`, `when` need trailing `then`)
+   * Match coding style (+if+, +elsif+, +when+ need trailing +then+)
 
-3. Don't modify the history file or version number.
+3. If any new files are added or existing files removed in a commit or PR, please update the +Manifest.txt+ accordingly.
 
-4. If you have any questions, just ask on IRC in #rubygems on Freenode or file
+4. Don't modify the history file or version number.
+
+5. If you have any questions, just ask on IRC in #rubygems on Freenode or file
    an issue here: http://github.com/rubygems/rubygems/issues
 
 For more information and ideas on how to contribute to RubyGems ecosystem, see
@@ -26,7 +28,7 @@ here: http://guides.rubygems.org/contributing/
     $ gem install hoe
     $ rake newb
 
-To run commands like `gem install` from the repo:
+To run commands like <tt>gem install</tt> from the repo:
 
     $ ruby -Ilib bin/gem install
 
@@ -36,59 +38,65 @@ RubyGems uses labels to track all issues and pull requests. In order to provide
 guidance to the community this is documentation of how labels are used in the
 rubygems repository.
 
+=== Contribution
+
+These labels are made to guide contributors to issue/pull requests that they
+can help with. That are marked with a light gray <tt>contribution: *</tt>
+
+* *small* - The issue described here will take a small amount of work to resolve,
+  and is a good option for a new contributor
+* *unclaimed* - The issue has not been claimed for work, and is awaiting willing
+  volunteers!
+
 === Type
 
-Most Issues or pull requests will have one of these labels, which describes the
-type of the issue or pull request.
+Most Issues or pull requests will have a light green <tt>type: *</tt> label, 
+which describes the type of the issue or pull request.
 
 * <b>bug report</b> - An issue describing a bug in rubygems. This would be something
   that is broken, confusing, unexpected behavior etc.
-* <b>bugfix</b> - A pull request that fixes a bug report.
+* <b>bug fix</b> - A pull request that fixes a bug report.
 * <b>feature request</b> - An issue describing a request for a new feature or
   enhancement.
 * <b>feature implementation</b> - A pull request implementing a feature request.
-* <b>question</b> - An issue that is a more of a question than a call for specific
+* *question* - An issue that is a more of a question than a call for specific
   changes in the codebase.
-* <b>cleanup</b> - Generally for a pull request that improves the code base without
+* *cleanup* - Generally for a pull request that improves the code base without
   fixing a bug or implementing a feature.
 * <b>major bump</b> - This issue or pull request requires a major version bump
-* <b>administrative</b> - This issue relates to adminstrative tasks that need to
+* *administrative* - This issue relates to administrative tasks that need to
   take place as it relates to rubygems
+* *documentation* - This issue relates to improving the documentation for
+  in this repo. Note that much of the rubygems documentation is here:
+  https://github.com/rubygems/guides
 
-Bug report and Bugfix have the same color. And feature implementation and
-feature request have the same color since they are related labels.
-
-=== Workflow
+=== Workflow / Status
 
-These are labels that indicate the state of an issue, where it is in the process
-from being submitted to being closed. These are listed in rough progression
-order from submitted to closed.
+The light yellow <tt>status: *</tt> labels that indicate the state of an 
+issue, where it is in the process from being submitted to being closed. 
+These are listed in rough  progression order from submitted to closed.
 
-* <b>triage</b> - This is an issue or pull request that needs to be properly
+* *triage* - This is an issue or pull request that needs to be properly
   labeled by by a maintainer.
-* <b>accepted</b> - This issue / pull request has been accepted as valid and
-  will be worked on by someone.
-* <b>ready for work</b> - An issue that is available for collaboration. This issue
+* *confirmed* - This issue/pull request has been accepted as valid, but
+  is not yet immediately ready for work.
+* <b>ready</b> - An issue that is available for collaboration. This issue
   should have existing discussion on the problem, and a description of how to go
-  about solving it. This label should be removed once someone has said they are
-  going to work on it.
-* <b>claimed</b> - An issue that is claimed by a member of the community and is
-  working on it. If the member can be assigned to the issue, they should be.
-* <b>feedback</b>- This issue/pull request is waiting on feedback from
-  one ore more of the folks involved in the issue. Generally their should be an
-  <tt>@username/team</tt> in the issue indicating who should respond.
-* <b>blocked</b> - the issue/pull request is currently unable to move forward because
-  of some specific reason, generally this will be a reason that is outside
+  about solving it.
+* <b>working</b> - An issue that has a specific invidual assigned to and planning
+  to do work on it.
+* <b>user feedback required</b> - The issue/pull request is blocked pending more
+  feedback from an end user
+* <b>blocked / backlog</b> - the issue/pull request is currently unable to move forward
+  because of some specific reason, generally this will be a reason that is outside
   RubyGems or needs feedback from some specific individual or group, and it may
   be a while before something it is resolved.
 
-Feedback and blocked all have the same color since they are all waiting on
-someone in particular to do something.
-
-=== Inactive Reason
+=== Closed Reason
 
 Reasons are why an issue / pull request was closed without being worked on or
-accepted. There should also be more detailed information in the comments.
+accepted. There should also be more detailed information in the comments. The
+closed reason labels are maroon <tt>closed: *</tt>.
 
 * *duplicate* - This is a duplicate of an existing bug. The comments must
   reference the existing issue.
@@ -98,32 +106,25 @@ accepted. There should also be more detailed information in the comments.
   is not accepted.
 * *deprecated* - An issue/pull request that no longer applies to the actively
   maintained codebase.
-
-All the reason labels are the same maroon color.
+* *discussion* - An issue/pull that is no longer about a concrete change, and
+  is instead being used for discussion.
 
 === Categories
 
 These are aspects of the codebase, or what general area the issue or pull
-request pertains too. Not all issues will have a category.
+request pertains too. Not all issues will have a category. All categorized
+issues have a blue <tt>category: *</tt> label.
 
-* <b>gemspec</b> - related to the gem specification itself
-* <b>API</b> - related to the public supported rubygems API. This is the code api,
+* *gemspec* - related to the gem specification itself
+* *API* - related to the public supported rubygems API. This is the code API,
   not a network related API.
-* <b>command</b> - related to something in <tt>Gem::Commands</tt>
-* <b>install</b> - related to gem installations
-* <b>documentation</b> - related to updating / fixing / clarifiying documentation or
+* *command* - related to something in <tt>Gem::Commands</tt>
+* *install* - related to gem installations
+* *documentation* - related to updating / fixing / clarifying documentation or
   guides
 
-All category labels are the same blue color.
-
 === Platforms
 
 If an issue or pull request pertains to only one platform, then it should have
-an appropriate platform tag.
-
-* *windows*
-* *java*
-* *osx*
-* *linux*
-
-All platform tags are the same purple color.
+an appropriate purple <tt>platform: *</tt> label. Current platform labels:
+*windows*, *java*, *osx*, *linux*