mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Clarify maintenance policy for bug fixes to security patches
The policy for security patches is very strict, and some people may find it surprising that even breaking changes as a result of an oversight or bug in a security fix will neither receive a release of their own nor be included in any subsequent security patches to address other security issues. Hopefully this additional text will help clarify this and avoid confusion.
This commit is contained in:
parent
b9b218f2ab
commit
e192fdddcf
1 changed files with 5 additions and 0 deletions
|
@ -59,6 +59,11 @@ be built from 1.2.2, and then added to the end of 1-2-stable. This means that
|
||||||
security releases are easy to upgrade to if you're running the latest version
|
security releases are easy to upgrade to if you're running the latest version
|
||||||
of Rails.
|
of Rails.
|
||||||
|
|
||||||
|
Only direct security patches will be included in security releases. Fixes for
|
||||||
|
non-security related bugs resulting from a security patch may be published on a
|
||||||
|
release's x-y-stable branch, and will only be released as a new gem in
|
||||||
|
accordance with the Bug Fixes policy.
|
||||||
|
|
||||||
**Currently included series:** `7.0.Z`, `6.1.Z`, `5.2.Z`.
|
**Currently included series:** `7.0.Z`, `6.1.Z`, `5.2.Z`.
|
||||||
|
|
||||||
Severe Security Issues
|
Severe Security Issues
|
||||||
|
|
Loading…
Reference in a new issue