From 713b3c82daf177631bd52ad42cd0b7cfd642bb22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Arko?= Date: Mon, 20 Jan 2020 01:13:19 -0800 Subject: =?UTF-8?q?=E2=9C=82=EF=B8=8F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit removes trailing whitespace (I hope) --- doc/POLICIES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- cgit v1.2.1