Merge branch '1.13' into 1.14

* 1.13:
  [Behat] Use chromedrives in some scenarios
  Update PR template
  [Documentation] Update release cycle after 1.13 release
This commit is contained in:
Grzegorz Sadowski 2024-04-29 10:44:38 +02:00
commit 73fdf8ea29
No known key found for this signature in database
GPG key ID: EF87FF4E6E3BD364
2 changed files with 21 additions and 20 deletions

View file

@ -1,16 +1,17 @@
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 or 1.13 <!-- see the comment below --> |
| Bug fix? | no/yes |
| New feature? | no/yes |
| BC breaks? | no/yes |
| Deprecations? | no/yes <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | fixes #X, partially #Y, mentioned in #Z |
| License | MIT |
| Q | A
|-----------------|-----
| Branch? | 1.12, 1.13, 1.14 or 2.0 <!-- see the comment below -->
| Bug fix? | no/yes
| New feature? | no/yes
| BC breaks? | no/yes
| Deprecations? | no/yes <!-- don't forget to update the UPGRADE-*.md file -->
| Related tickets | fixes #X, partially #Y, mentioned in #Z
| License | MIT
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Bug fixes must be submitted against the 1.12 or 1.13 branches
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted against the 2.0 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:

View file

@ -47,23 +47,21 @@ Maintenance
Each minor Sylius version is maintained for a fixed period of time after its release.
This maintenance is divided into:
* *Bug fixes and security fixes*: During this period, being *eight months* long,
all issues can be fixed. The end of this period is referenced as being the
*end of maintenance* of a release.
* *Bug fixes and security fixes*: During this period all issues can be fixed.
The end of this period is referenced as being the *end of maintenance* of a release.
* *Security fixes only*: During this period, being *sixteen months* long,
only security related issues can be fixed. The end of this period is referenced
as being the *end of life* of a release.
* *Security fixes only*: During this period, only security related issues can be fixed.
The end of this period is referenced as being the *end of life* of a release.
Future release
--------------
Planned releases
----------------
+---------+----------------------+------------------------+--------------------+
| Version | Development starts | Stabilization starts | Release date |
+=========+======================+========================+====================+
| 2.0 | Sep 15, 2023 | Q2 2024 | Q3 2024 |
+---------+----------------------+------------------------+--------------------+
| 1.13 | Oct 31, 2022 | Feb 15, 2024 | Apr 23, 2024 |
| 1.14 | Apr 26, 2024 | Q2 2024 | Q3 2024 |
+---------+----------------------+------------------------+--------------------+
Supported versions
@ -72,6 +70,8 @@ Supported versions
+---------+--------------------+--------------------+--------------------+-----------------------+
| Version | Release date | End of maintenance | End of life | Status |
+=========+====================+====================+====================+=======================+
| 1.13 | Apr 23, 2024 | Oct 23, 2024 | Apr 23, 2025 | Fully supported |
+---------+--------------------+--------------------+--------------------+-----------------------+
| 1.12 | Oct 31, 2022 | Jun 30, 2024 | Dec 31, 2024 | Fully supported |
+---------+--------------------+--------------------+--------------------+-----------------------+