From 2fa921935326a78a093b028048428e304875ee46 Mon Sep 17 00:00:00 2001 From: knsv Date: Fri, 2 Feb 2024 07:56:48 +0000 Subject: [PATCH] Update docs --- docs/community/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/community/contributing.md b/docs/community/contributing.md index d6afbd90d..badd821d0 100644 --- a/docs/community/contributing.md +++ b/docs/community/contributing.md @@ -370,7 +370,7 @@ If the users have no way to know that things have changed, then you haven't real Likewise, if users don't know that there is a new feature that you've implemented, it will forever remain unknown and unused. The documentation has to be updated for users to know that things have been changed and added! -If you are adding a new feature, add `(v+)` in the title or description. It will be replaced automatically with the current version number when the release happens. +If you are adding a new feature, add `(v10.8.0+)` in the title or description. It will be replaced automatically with the current version number when the release happens. eg: `# Feature Name (v+)`