Skip to content

Releases: add details to minor and major versions #16928

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.

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

Merged
merged 1 commit into from
Jul 6, 2022
Merged
Changes from all commits
Commits
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
8 changes: 5 additions & 3 deletions contributing/community/releases.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,11 @@ published through a *time-based model*:
* A new **Symfony patch version** (e.g. 4.4.12, 5.1.9) comes out roughly every
month. It only contains bug fixes, so you can safely upgrade your applications;
* A new **Symfony minor version** (e.g. 4.4, 5.0, 5.1) comes out every *six months*:
one in *May* and one in *November*. It contains bug fixes and new features, but
it doesn't include any breaking change, so you can safely upgrade your applications;
* A new **Symfony major version** (e.g. 4.0, 5.0) comes out every *two years*.
one in *May* and one in *November*. It contains bug fixes and new features,
can contain new deprecations but it doesn't include any breaking change,
so you can safely upgrade your applications;
* A new **Symfony major version** (e.g. 4.0, 5.0) comes out every *two years*
in November of odd years (e.g. 2019, 2021).
It can contain breaking changes, so you may need to do some changes in your
applications before upgrading.

Expand Down