From f3b60a1dabead08d31cf19cd1a52a4d2e1364324 Mon Sep 17 00:00:00 2001 From: curquiza Date: Sun, 20 Jul 2025 22:20:08 +0200 Subject: [PATCH] Minor update on doc --- documentation/release.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/release.md b/documentation/release.md index 4d8bb0016..f308bab98 100644 --- a/documentation/release.md +++ b/documentation/release.md @@ -4,9 +4,9 @@ This guide is to describe how to make releases for the current repository. ## 📅 Weekly Meilisearch release -1. A weekly meeting is done every Monday to define the release and check the following information +1. A weekly meeting is done every Monday to define the release and to ensure minimal checks before the release.
-👇👇👇 +Check out the TODO 👇👇👇 - [ ] Define the version of the release (`vX.Y.Z`) - [ ] Manually test `--experimental-dumpless-upgrade` on a DB of the previous Meilisearch minor version
- [ ] Check recent automated tests on `main`
@@ -19,9 +19,9 @@ This guide is to describe how to make releases for the current repository. - [ ] Create the PR updating the versionand merge it.
-1. Go to the GitHub interface, in the [`Release` section](https://github.com/meilisearch/meilisearch/releases). +2. Go to the GitHub interface, in the [`Release` section](https://github.com/meilisearch/meilisearch/releases). -2. Select the already drafted release or click on the `Draft a new release` button if you want to start a blank one, and fill the form with the appropriate information. +3. Select the already drafted release or click on the `Draft a new release` button if you want to start a blank one, and fill the form with the appropriate information. ⚠️ Publish on `main` ⚙️ The CIs will be triggered to: