JezK
Edit File: page-POLICIES_rdoc.ri
U:RDoc::TopLevel[ i I"POLICIES.rdoc:ETcRDoc::Parser::Simpleo:RDoc::Markup::Document:@parts[,S:RDoc::Markup::Heading: leveli: textI"Pull Requests;To:RDoc::Markup::BlankLine o:RDoc::Markup::Paragraph;[I"PContributions to RubyGems are made via GitHub pull requests, which must be ;TI"Oapproved by a project committer other than the author. To approve a PR, a ;TI"Smaintainer can leave a comment including the text "@homu r+", indicating that ;TI"Pthey have reviewed the PR and approve it. [Homu](http://homu.io) will then ;TI"Qautomatically create a merge commit, test the merge, and land the PR if the ;TI"#merge commit passes the tests.;T@ o; ;[I"RThis process guarantees that our release branches always have passing tests, ;TI"Tand reduces siloing of information to a single contributor. For a full list of ;TI"Epossible commands, see [the Homu documentation](http://homu.io).;T@ S; ; i;I"Long-Term Support;T@ o; ;[I"NRubyGems long-term support policy will be similar to and follow the Ruby ;TI"long-term support policy.;T@ o; ;[ I"TWhen a Ruby version reaches end-of-life, the RubyGems version included in that ;TI"Urelease will also reach end-of-life. After that date no security releases will ;TI"Tbe made for RubyGems releases up to the version shipped in the next release of ;TI" Ruby.;T@ o; ;[ I"PFor example, Ruby 1.9.3 reached end-of-life on 23 February 2015. RubyGems ;TI"Qversion 2.0.0 shipped with Ruby 2.0.0, so no RubyGems versions earlier than ;TI"T2.0.0 will receive any updates. Ruby 2.1.0 shipped with RubyGems 2.2.0. When ;TI"QRuby 2.0.0 reaches end-of-life no RubyGems versions earlier than 2.2.0 will ;TI"receive any updates.;T@ S; ; i;I"Security Fixes;T@ o; ;[I"SSecurity releases will be made for RubyGems version series that were included ;TI"in a Ruby release.;T@ o; ;[I"NFor example, RubyGems 2.0.x will receive security fixes until Ruby 2.0.0 ;TI"reaches end-of-life.;T@ S; ; i;I"Release Policies;T@ o; ;[I"URubyGems primarily makes bug fix releases off of the master branch. We may mix ;TI"Rbug fixes and new features in the same release. RubyGems does not guarantee ;TI"8it will make bug fix releases for earlier versions.;T@ o; ;[I"KFor example, RubyGems 2.5.0 was recently released. RubyGems does not ;TI"Tguarantee any non-security bugfix releases will be made upon the 2.4.x series, ;TI"(or any earlier series, of releases.;T@ o; ;[I"TAdditionally, when a Ruby version reaches end-of-life the following release of ;TI"RRubyGems will no longer be required to maintain backwards compatibility with ;TI"Cthat Ruby version. This may result in a major version change.;T@ o; ;[ I"MFor example, since Ruby 1.9.3 has reached end-of-life, RubyGems may use ;TI"Qfeatures of ruby that only exist in Ruby 2.0 and later. As of this writing ;TI"LRubyGems is 2.5.x, so the RubyGems version would become 3.x if it used ;TI"3features only available in Ruby 2.0 and later.;T@ S; ; i;I"Committer Access;T@ o; ;[I"SRubyGems committers may lose their commit privileges if they are inactive for ;TI"Rlonger than 12 months. Committer permission may be restored upon request by ;TI""having a pull request merged.;T@ o; ;[ I"NThis is designed to improve the maintainability of RubyGems by requiring ;TI"Rcommitters to maintain familiarity with RubyGems activity and to improve the ;TI"Qsecurity of RubyGems by preventing idle committers from having their commit ;TI"(permissions compromised or exposed.;T@ S; ; i;I"Changing These Policies;T@ o; ;[ I"QThese policies were set in order to reduce the burden of maintenance and to ;TI"Tkeep committers current with existing development and policies. RubyGems work ;TI"Qis primarily volunteer-driven which limits the ability to provide long-term ;TI"Msupport. By funding RubyTogether you can help extend support for older ;TI"RubyGems versions.;T: @file@:0@omit_headings_from_table_of_contents_below0