Skip to content
Permalink
Browse files

Update versions in SECURITY_POLICY after release of 2.2

  • Loading branch information
jeremyevans committed Feb 9, 2020
1 parent b9262d6 commit fd968b414f7b94ed124245c1adbe8ffaa371c543
Showing with 5 additions and 5 deletions.
  1. +5 −5 SECURITY_POLICY.md
@@ -10,21 +10,21 @@ New features will only be added to the master branch and will not be made availa

Only the latest release series will receive bug fixes. When enough bugs are fixed and its deemed worthy to release a new gem, this is the branch it happens from.

* Current release series: 2.1.x
* Current release series: 2.2.x

### Security issues

The current release series and the next most recent one will receive patches and new versions in case of a security issue.

* Current release series: 2.1.x
* Next most recent release series: 2.0.x
* Current release series: 2.2.x
* Next most recent release series: 2.1.x

### Severe security issues

For severe security issues we will provide new versions as above, 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.

* Current release series: 2.1.x
* Next most recent release series: 2.0.x
* Current release series: 2.2.x
* Next most recent release series: 2.1.x
* Last major release series: 1.6.x

### Unsupported Release Series

0 comments on commit fd968b4

Please sign in to comment.
You can’t perform that action at this time.