From 38777459556d8ed6be261d32d7ea2d7d7f8caa4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=AD=20Bol=C3=ADvar?= Date: Mon, 20 Feb 2023 10:15:34 -0800 Subject: [PATCH] MAINTAINERS.rst: updates MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Keep track of other things we do that aren't mentioned yet. Signed-off-by: Martí Bolívar --- MAINTAINERS.rst | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/MAINTAINERS.rst b/MAINTAINERS.rst index f7156a2..a79fce1 100644 --- a/MAINTAINERS.rst +++ b/MAINTAINERS.rst @@ -64,10 +64,19 @@ Pre-release test plan (It's still a pass if ``west build`` requires ``--pristine``.) -7. Assuming that all went well (if it didn't, go fix it and repeat), update - __version__ to 'X.Y.Z' (i.e. drop the 'aN' suffix that denotes alpha N), tag - the release (see "Tagging the release" for a procedure) and upload to PyPI - (see "Building and uploading the release wheels" for a procedure). +7. Assuming that all went well (if it didn't, go fix it and repeat): + + - update __version__ to 'X.Y.Z' (i.e. drop the 'aN' suffix that denotes + alpha N) + + - tag the release on GitHub (see "Tagging the release" for a procedure) + + - create a release on GitHub from the new tag by going to + https://github.com/zephyrproject-rtos/west/releases + clicking "Draft a new release", and following instructions + + - upload the release artifacts to PyPI (see "Building and uploading the + release wheels" for a procedure) 8. Send email to the Zephyr lists, announce@ and users@, notifying them of the new release. Include 'git shortlog' data of the new commits since the last