summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndré Arko <andre@arko.net>2020-01-20 01:13:19 -0800
committerGitHub <noreply@github.com>2020-01-20 01:13:19 -0800
commit713b3c82daf177631bd52ad42cd0b7cfd642bb22 (patch)
tree960a2fcbaabf7358cade34af16b3d937ccae1c70
parent4c0e9f9488b02af6bc8fd965ce158b3f6ecf5b8b (diff)
downloadbundler-713b3c82daf177631bd52ad42cd0b7cfd642bb22.tar.gz
✂️
removes trailing whitespace (I hope)
-rw-r--r--doc/POLICIES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/POLICIES.md b/doc/POLICIES.md
index 46f10c797e..e4a9243374 100644
--- a/doc/POLICIES.md
+++ b/doc/POLICIES.md
@@ -29,7 +29,7 @@ Minor/feature releases can be cut anytime at least one new feature is ready, but
Major version releases should be cut no more than once per year, and must include a new section of the website with documentation for that major version.
-Major releases ideally happen after a Ruby version loses support in February or March, which helps us stay in sync with Ruby versions uspported by the core team.
+Major releases ideally happen after a Ruby version loses support in February or March, which helps us stay in sync with Ruby versions uspported by the core team.
Breaking changes other than dropping support for old Ruby versions should be avoided whenever possible, but may be included in major releases. In general, breaking changes should include at least one major version (and one year elapsed) with a deprecation warning before the breaking change takes effect.