From b8f9550a2e19540cd19235cafaa05af801cf3bf6 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Mon, 25 Jan 2021 21:27:43 +0100 Subject: [PATCH] Update doc/articles/versions.md --- doc/articles/versions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/versions.md b/doc/articles/versions.md index 5f5515930..67f2c2958 100644 --- a/doc/articles/versions.md +++ b/doc/articles/versions.md @@ -85,7 +85,7 @@ When branch names look like versions, we have to clarify for composer that we're Composer recognizes the following stabilities (in order of stability): dev, alpha, beta, RC, and stable where RC stands for release candidate. The stability of a version is defined by its suffix e.g version `v1.1-BETA` has a stability of -`beta` and `v1.1-RC1` has a stability of `rc`. If such a suffix is missing +`beta` and `v1.1-RC1` has a stability of `RC`. If such a suffix is missing e.g. version `v1.1` then Composer considers that version `stable`. In addition to that Composer automatically adds a `-dev` suffix to all numeric branches and prefixes all other branches imported from a VCS repository with `dev-`. In both