From 865553dbe3e30125701b584a4d1aaa49e3d0930e Mon Sep 17 00:00:00 2001 From: Leonardo Grasso Date: Wed, 10 Jan 2024 16:02:46 +0100 Subject: [PATCH] docs(proposals/20231220-features-adoption-and-deprecation): only stable features deprecation require a major bump Signed-off-by: Leonardo Grasso --- proposals/20231220-features-adoption-and-deprecation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/20231220-features-adoption-and-deprecation.md b/proposals/20231220-features-adoption-and-deprecation.md index 66dc7335..ce989925 100644 --- a/proposals/20231220-features-adoption-and-deprecation.md +++ b/proposals/20231220-features-adoption-and-deprecation.md @@ -181,7 +181,7 @@ Regarding the above policies, component versioning must adhere to [Semantic Vers Thus, given a version number `MAJOR.MINOR.PATCH` increment the: -- *MAJOR* version when the deprecation period ends, thus introducing incompatible user-facing or API changes. +- *MAJOR* version when the deprecation period of one or more _stable_ features ends, thus introducing incompatible user-facing or API changes. - *MINOR* version when adding functionality in a backward-compatible manner. - *PATCH* version when making backward-compatible bug fixes.