From 427daab868cd9b84cc4a343110040f879aac5f64 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Thu, 10 Dec 2015 11:49:38 +0100 Subject: [PATCH] Minor changes --- contributing/community/releases.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/contributing/community/releases.rst b/contributing/community/releases.rst index 842bbf5f128..f7a931063ec 100644 --- a/contributing/community/releases.rst +++ b/contributing/community/releases.rst @@ -9,9 +9,8 @@ Symfony manages its releases through a *time-based model* and follows the * A new Symfony minor version (e.g. 2.8, 3.2, 4.1) comes out every *six months*: one in *May* and one in *November*; -* A new Symfony major version (e.g., 3.0.0, 4.0.0) comes out every *two years* - and it's released at the same time of the last minor version of the previous - branch. +* A new Symfony major version (e.g., 3.0, 4.0) comes out every *two years* and + it's released at the same time of the last minor version of the previous branch. .. note:: @@ -93,7 +92,7 @@ Below is the schedule for the first few versions that use this release model: :align: center * **Yellow** represents the Development phase -* **Blue** represents the Stabilisation phase +* **Blue** represents the Stabilization phase * **Green** represents the Maintenance period This results in very predictable dates and maintenance periods: