Update our security policy to include all releases in the current series

We don't want people to jump from the last release in the previous
series (4.2) straing to the first release in the current series that is
support (5.1), so we should be supporting the entire series for severe
security issues.

This will not be a problem because usually we only have 3 releases in a
series and backporting patches inside the same series is not harder than
backporting to a previous series.
This commit is contained in:
Rafael Mendonça França 2018-04-10 18:38:33 -04:00
parent 686f4f3a94
commit 22b0a30215
No known key found for this signature in database
GPG Key ID: FC23B6D0F1EEE948
1 changed files with 2 additions and 2 deletions

View File

@ -64,11 +64,11 @@ of Rails.
Severe Security Issues
----------------------
For severe security issues we will provide new versions as above, and also the
For severe security issues all releases in the current series, and also the
last major release series will receive patches and new versions. The
classification of the security issue is judged by the core team.
**Currently included series:** `5.2.Z`, `5.1.Z`, `4.2.Z`.
**Currently included series:** `5.2.Z`, `5.1.Z`, `5.0.Z`, `4.2.Z`.
Unsupported Release Series
--------------------------