From 8c6b6700bc1483f01e2531f4177c668a41a31405 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Thu, 6 Jan 2022 06:32:46 -1000 Subject: [PATCH] ;doc: RELEASING: latest procedures --- RELEASING.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index b0ff6269b..24bdd8e52 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -77,6 +77,34 @@ Here is the normal release/build schedule (as of 2022): - Develop a process for making test releases at any time. - Establish routine weekly test releases. +## Procedures + +### Preview release +- ensure master is in releasable state +- `./Shake changelogs`, edit, commit (`./Shake changelogs -c`) +- `tools/release prep OLDMA.JOR.99.PREVIEW` (eg 1.24.99.1 for 1.25 preview 1) +- edit changelogs, amend commit +- `make functest` +- `tools/release bin` +- babysit/debug/repeat CI binary jobs until all succeed +- tag +- github release + - push commits & tags + - draft + - test + - publish + +### Major release +- as above, with MA.JOR +- other major release stuff - release notes, site updates, hackage, announce +- merge release changelog back to master +- bump version in master + +### Minor/Fixup release +- switch to release branch +- cherry pick changes from master +- proceed as above, with MA.JOR.MINOR[.FIXUP] + ---- ## Review/update/consolidate: