From f1a49fe7799f85f1dbde45ada6f3c97150146da5 Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@victoriametrics.com>
Date: Sat, 30 Jul 2022 00:15:49 +0300
Subject: [PATCH] docs/Release-Guide.md: document that feature docs must be
updated with the release where the feature appeared
---
docs/Release-Guide.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/Release-Guide.md b/docs/Release-Guide.md
index 0e08e3557a..b2652f1d96 100644
--- a/docs/Release-Guide.md
+++ b/docs/Release-Guide.md
@@ -7,7 +7,8 @@ sort: 18
## Release version and Docker images
0. Make sure that the release commits have no security issues.
-1. Document all the changes for new release in [CHANGELOG.md](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/CHANGELOG.md).
+1a. Document all the changes for new release in [CHANGELOG.md](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/docs/CHANGELOG.md).
+1b. Add `(available in v1.xx.y)` line to feature docs introduced in the upcoming release.
2. Create the following release tags:
* `git tag -s v1.xx.y` in `master` branch
* `git tag -s v1.xx.y-cluster` in `cluster` branch