minor #16928 Releases: add details to minor and major versions (alexislefebvre)

This PR was squashed before being merged into the 4.4 branch.

Discussion
----------

Releases: add details to minor and major versions

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Commits
-------

4ae363a Releases: add details to minor and major versions

Author: javiereguiluz

contributing/community/releases.rst

@@ -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.