From d7d451a9bc9bd8a35e8cdb954f9df3c9ed236b69 Mon Sep 17 00:00:00 2001 From: Charles Beauville Date: Thu, 12 Oct 2023 17:13:52 +0200 Subject: [PATCH] Fix release doc format (#2510) --- doc/source/contributor-how-to-release-flower.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/source/contributor-how-to-release-flower.rst b/doc/source/contributor-how-to-release-flower.rst index c67a7d46f798..cb33cf0b3c3f 100644 --- a/doc/source/contributor-how-to-release-flower.rst +++ b/doc/source/contributor-how-to-release-flower.rst @@ -18,8 +18,7 @@ During the release The version number of a release is stated in ``pyproject.toml``. To release a new version of Flower, the following things need to happen (in that order): 1. Update the ``changelog.md`` section header ``Unreleased`` to contain the version number and date for the release you are building. Create a pull request with the change. -2. Tag the release commit with the version number as soon as the PR is merged: ``git tag v0.12.3``, then ``git push --tags``. This will create a draft release on GitHub -containing the correct artifacts and the relevant part of the changelog. +2. Tag the release commit with the version number as soon as the PR is merged: ``git tag v0.12.3``, then ``git push --tags``. This will create a draft release on GitHub containing the correct artifacts and the relevant part of the changelog. 3. Check the draft release on GitHub, and if everything is good, publish it. After the release