Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DOC Clarify that we could upgrade a fixed dependency to add support for a newer PHP release #148

Merged
merged 1 commit into from
Feb 2, 2023
Merged

DOC Clarify that we could upgrade a fixed dependency to add support for a newer PHP release #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion en/06_Project_Governance/05_Major_release_policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,11 @@ At launch, Silverstripe CMS major releases aim to have all PHP and JavaScript de

A list of *fixed dependencies* for each Silverstripe CMS major release line is explicitly defined by the development team. *Fixed dependencies* do not change for the lifetime of a Silverstripe CMS major release line.

Support for newer major releases of fixed dependencies is not added to Silverstripe CMS major release line, even if the currently used version is end-of-life. The only exception is if the upgrade is necessary to fix a high impact bug or security vulnerability. A Silverstripe CMS major release line only supports one major version of each fixed dependency.
Support for newer major releases of fixed dependencies is not added to Silverstripe CMS major release line, even if the currently used version is end-of-life. A Silverstripe CMS major release line only supports one major version of each fixed dependency.

The only exceptions are:
- if the upgrade is necessary to fix a high impact bug or security vulnerability
- if the upgrade is necessary to add support for a new PHP version to a Silverstripe CMS major release in active development.

Non-fixed dependencies may be upgraded to new major releases or swapped out altogether within a Silverstripe CMS release line.

Expand Down