File tree 2 files changed +4
-4
lines changed 2 files changed +4
-4
lines changed Original file line number Diff line number Diff line change 11<!--
22
33If your pull request fixes a BUG, use the oldest maintained branch that contains
4- the bug (see https://symfony.com/roadmap for the list of maintained branches).
4+ the bug (see https://symfony.com/releases for the list of maintained branches).
55
66If your pull request documents a NEW FEATURE, use the same Symfony branch where
77the feature was introduced (and `master` for features of unreleased versions).
Original file line number Diff line number Diff line change @@ -7,12 +7,12 @@ release and maintain its different versions.
77Symfony releases follow the `semantic versioning `_ strategy and they are
88published through a *time-based model *:
99
10- * A new **Symfony patch version ** (e.g. 3 .4.41, 4.4.9 ) comes out roughly every
10+ * A new **Symfony patch version ** (e.g. 4 .4.9, 5.0.9, 5.1.1 ) comes out roughly every
1111 month. It only contains bug fixes, so you can safely upgrade your applications;
12- * A new **Symfony minor version ** (e.g. 4.4, 5.0, 5. 1) comes out every *six months *:
12+ * A new **Symfony minor version ** (e.g. 4.4, 5.1) comes out every *six months *:
1313 one in *May * and one in *November *. It contains bug fixes and new features, but
1414 it doesn't include any breaking change, so you can safely upgrade your applications;
15- * A new **Symfony major version ** (e.g. 4.0, 5.0) comes out every *two years *.
15+ * A new **Symfony major version ** (e.g. 4.0, 5.0, 6.0 ) comes out every *two years *.
1616 It can contain breaking changes, so you may need to do some changes in your
1717 applications before upgrading.
1818
You can’t perform that action at this time.
0 commit comments