Update releases.rst

contributing/community/releases.rst

@@ -7,9 +7,9 @@ release and maintain its different versions.
 Symfony releases follow the `semantic versioning`_ strategy and they are
 published through a *time-based model*:
 
-* A new **Symfony patch version** (e.g. 4.4.12, 5.1.9) comes out roughly every
+* A new **Symfony patch version** (e.g. 4.4.43, 5.4.10, 6.1.2) 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*:
+* A new **Symfony minor version** (e.g. 4.4, 5.4, 6.1) comes out every *six months*:
   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;
@@ -19,14 +19,21 @@ published through a *time-based model*:
 
 .. tip::
 
-    `Subscribe to Symfony Roadmap notifications`_ to receive an email when a new
+    `Subscribe to Symfony Release notifications`_ to receive an email when a new
     Symfony version is published or when a Symfony version reaches its end of life.
 
 .. _contributing-release-development:
 
 Development
 -----------
 
+.. note::
+
+    The Symfony project is an open-source community driven development framework.
+    There is no roadmap written or defined in advance. Every feature request
+    may or may not be developed in future version based on the community.
+    Symfony core team members can help move things forward if the intereset is here.
+
 The full development period for any major or minor version lasts six months and
 is divided into two phases:
 
@@ -43,7 +50,7 @@ final release.
 
 .. tip::
 
-    Check out the `Symfony Roadmap`_ to learn more about any specific version.
+    Check out the `Symfony Release`_ to learn more about any specific version.
 
 .. _contributing-release-maintenance:
 .. _symfony-versions:
@@ -93,12 +100,12 @@ two versions: the new major one (e.g. 5.0) and the latest version of the
 previous branch (e.g. 4.4).
 
 Both versions have the same new features, but they differ in the deprecated
-features. The oldest version (4.4 in this example) contains all the deprecated
-features whereas the new version (5.0 in this example) removes all of them.
+features. The oldest version (5.4 in this example) contains all the deprecated
+features whereas the new version (6.0 in this example) removes all of them.
 
-This allows you to upgrade your projects to the latest minor version (e.g. 4.4),
+This allows you to upgrade your projects to the latest minor version (e.g. 5.4),
 see all the deprecation messages and fix them. Once you have fixed all those
-deprecations, you can upgrade to the new major version (e.g. 5.0) without
+deprecations, you can upgrade to the new major version (e.g. 6.0) without
 effort, because it contains the same features (the only difference are the
 deprecated features, which your project no longer uses).
 
@@ -155,6 +162,6 @@ period to upgrade. Companies wanting more stability use the LTS versions: a new
 version is published every two years and there is a year to upgrade.
 
 .. _`semantic versioning`: https://semver.org/
-.. _`Subscribe to Symfony Roadmap notifications`: https://symfony.com/account/notifications
-.. _`Symfony Roadmap`: https://symfony.com/releases
+.. _`Subscribe to Symfony Release notifications`: https://symfony.com/account/notifications
+.. _`Symfony Release`: https://symfony.com/releases
 .. _`professional Symfony support`: https://sensiolabs.com/