diff options
| author | André Arko <andre@arko.net> | 2020-01-19 23:58:10 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-19 23:58:10 -0800 |
| commit | 4c0e9f9488b02af6bc8fd965ce158b3f6ecf5b8b (patch) | |
| tree | 6a44e2afe0b6cbb7a268710ad11fc95e8c87d4e6 | |
| parent | 7fd3a1bde6e79db8dd85d172febfe5b2942e6d95 (diff) | |
| download | bundler-4c0e9f9488b02af6bc8fd965ce158b3f6ecf5b8b.tar.gz | |
Return backporting caveat
I didn't actually mean to delete this paragraph, whoops
| -rw-r--r-- | doc/POLICIES.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/POLICIES.md b/doc/POLICIES.md index 4c810c284f..46f10c797e 100644 --- a/doc/POLICIES.md +++ b/doc/POLICIES.md @@ -19,6 +19,8 @@ Bundler will provide features and bugfixes to older versions on a schedule simil Bundler supports Ruby and RubyGems versions until the next major release after the Ruby core team drops support. For example, the Ruby core team will drop all Ruby 2.4 support on March 31, 2020. The next Bundler major release after that date will drop support for Ruby 2.4. +These policies are not a guarantee that any particular fix will be backported. Instead, this is a way for us to set an upper limit on the versions of Ruby, RubyGems, and Bundler that we have to consider while making changes. Without the limit, the number of versions grows exponentially over time and quickly becomes overwhelming, which leads to maintainer burnout. We want to avoid that. + ### Release guidelines Bugfix releases should generally be cut as soon as possible. A bugfix release for a single PR is totally okay. |