From fb875c9014ba5742f8b60d0a6503046bd2d2297d Mon Sep 17 00:00:00 2001
From: Florent Poinsard <35779988+frouioui@users.noreply.github.com>
Date: Wed, 11 Oct 2023 23:57:49 -0500
Subject: [PATCH] Mention roadmap planning/modification in the release process
 (#14254)

---
 doc/internal/release/how-to-release.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/internal/release/how-to-release.md b/doc/internal/release/how-to-release.md
index 628beb151b7..1d463c088da 100644
--- a/doc/internal/release/how-to-release.md
+++ b/doc/internal/release/how-to-release.md
@@ -144,6 +144,9 @@ On the release day, there are several things to do:
 Once the release is over, we need to announce it on both Slack and Twitter. We also want to make sure the blog post was cross-posted, if applicable.
 We need to verify that _arewefastyet_ has finished the benchmark too.
 
+Moreover, once the roadmap discussions are over for the next release, we need to update the roadmap presented in the Vitess website (https://vitess.io/docs/resources/roadmap/).
+We must remove everything that is now done in this release and add new items based on the discussions.
+
 -----
 
 ## How to prepare the release of Vitess