Skip to content

Commit 295ee02

Browse files
fabpotweaverryan
authored andcommitted
added information about security issue fixes, and made the timeline example clearer
1 parent 3081634 commit 295ee02

File tree

1 file changed

+33
-10
lines changed

1 file changed

+33
-10
lines changed

contributing/community/releases.rst

Lines changed: 33 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -33,18 +33,28 @@ Maintenance
3333
-----------
3434

3535
Each Symfony version is maintained for a fixed period of time, depending on
36-
the type of the release.
36+
the type of the release. We have two maintenance periods:
37+
38+
* *Bug fixes and security fixes*: During this period, all issues can be fixed.
39+
The end of this period is referenced as being the *end of maintenance* of a
40+
release.
41+
42+
* *Security fixes only*: During this period, only security related issues can
43+
be fixed. The end of this period is referenced as being the *end of
44+
life* of a release.
3745

3846
Standard Releases
3947
~~~~~~~~~~~~~~~~~
4048

41-
A standard release is maintained for an *eight month* period.
49+
A standard release is maintained for an *eight month* period for bug fixes,
50+
and for a *fourteen month* period for security issue fixes.
4251

4352
Long Term Support Releases
4453
~~~~~~~~~~~~~~~~~~~~~~~~~~
4554

4655
Every two years, a new Long Term Support Release (aka LTS release) is
47-
published. Each LTS release is supported for a *three year* period.
56+
published. Each LTS release is supported for a *three year* period for bug
57+
fixes, and for a *four year* period for security issue fixes.
4858

4959
.. note::
5060

@@ -63,14 +73,26 @@ Below is the schedule for the first few versions that use this release model:
6373
* **Blue** represents the Stabilisation phase
6474
* **Green** represents the Maintenance period
6575

66-
This results in very predictable dates and maintenance periods.
76+
This results in very predictable dates and maintenance periods:
77+
78+
| Version | Release | End of Maintenance | End of Life |
79+
| ------- | ------- | ------------------- | ----------- |
80+
| 2.0 | 07/2011 | 03/2013 (20 months) | 09/2013 |
81+
| 2.1 | 09/2012 | 05/2013 (9 months) | 11/2013 |
82+
| 2.2 | 03/2013 | 11/2013 (8 months) | 05/2014 |
83+
| **2.3** | 05/2013 | 05/2016 (36 months) | 05/2017 |
84+
| 2.4 | 11/2013 | 07/2014 (8 months) | 01/2015 |
85+
| 2.5 | 05/2014 | 01/2015 (8 months) | 07/2016 |
86+
| 2.6 | 11/2014 | 07/2015 (8 months) | 01/2016 |
87+
| **2.7** | 05/2015 | 05/2018 (36 months) | 05/2019 |
88+
| 2.8 | 11/2015 | 07/2016 (8 months) | 01/2017 |
89+
| ... | ... | ... | ... |
90+
91+
.. tip::
6792

68-
* *(special)* Symfony 2.2 will be released at the end of February 2013;
69-
* *(special)* Symfony 2.3 (the first LTS) will be released at the end of May
70-
2013;
71-
* Symfony 2.4 will be released at the end of November 2013;
72-
* Symfony 2.5 will be released at the end of May 2014;
73-
* ...
93+
If you want to learn more about the timeline of any given Symfony version,
94+
use the online `timeline calculator`_. You can also get all data as a JSON
95+
string via a URL like `http://symfony.com/roadmap.json?version=2.x`.
7496

7597
Backward Compatibility
7698
----------------------
@@ -124,3 +146,4 @@ upgrade.
124146

125147
.. _Git repository: https://github.com/symfony/symfony
126148
.. _SensioLabs: http://sensiolabs.com/
149+
.. _roadmap: http://symfony.com/roadmap

0 commit comments

Comments
 (0)