Skip to content

Commit 98dd82d

Browse files
committed
Add clarification on security releases
1 parent 92a7caa commit 98dd82d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

blog/2023-03-14-release-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Going forward, we plan to have 4 releases every year, one per quarter. We will a
1212
For example: our next release 20.1 will be in early April 2023, and this will be a feature and bugfix release without breaking changes. Therefore, we’re going to retain Java 8 in the April release. Our subsequent release will be in early July 2023 and will contain breaking changes, including upgrading to Java 11.
1313

1414
## Security backports
15-
We will backport critical bugfixes and security fixes for versions dating back 18 months (or roughly 6 versions). These fixes will be backported depending on severity and demand.
15+
We will backport critical bugfixes and security fixes for versions dating back 18 months (or roughly 6 versions). These fixes will be backported depending on severity and demand. As security fixes are time sensitive, we will release them on demand instead of waiting for the next quarterly release date.
1616

1717
## Bugfix backports
1818
We will backport important bug fixes at most 12 months (or roughly 4 versions). These fixes will be backported depending on the severity of the bug and demand.

0 commit comments

Comments
 (0)