From 654338f9c7c096377ad39afc39122fdd207ce3d1 Mon Sep 17 00:00:00 2001 From: Maxime Desroches Date: Thu, 18 Dec 2025 22:52:14 -0800 Subject: [PATCH] update release instructions --- release/README.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/release/README.md b/release/README.md index fb651fa05a..7aeea9fe4a 100644 --- a/release/README.md +++ b/release/README.md @@ -4,18 +4,17 @@ ## release checklist ### Go to staging -- [ ] make a GitHub issue to track release +- [ ] make a GitHub issue to track release with this checklist - [ ] create release master branch -- [ ] update RELEASES.md + - [ ] create a branch from upstream master named `zerotentwo` for release `v0.10.2` + - [ ] revert risky commits (double check with autonomy team) + - [ ] push the new branch +- [ ] push to staging: + - [ ] make sure you are on the newly created release master branch (`zerotentwo`) + - [ ] run `BRANCH=devel-staging release/build_stripped.sh`. Jenkins will then automatically build staging on device, run `test_onroad` and update the staging branch - [ ] bump version on master: `common/version.h` and `RELEASES.md` -- [ ] build new userdata partition from `release3-staging` - [ ] post on Discord, tag `@release crew` -Updating staging: -1. either rebase on master or cherry-pick changes -2. run this to update: `BRANCH=devel-staging release/build_devel.sh` -3. build new userdata partition from `release3-staging` - ### Go to release - [ ] before going to release, test the following: - [ ] update from previous release -> new release @@ -26,7 +25,7 @@ Updating staging: - [ ] check sentry, MTBF, etc. - [ ] stress test passes in production - [ ] publish the blog post -- [ ] `git reset --hard origin/release3-staging` +- [ ] `git reset --hard origin/release-mici-staging` - [ ] tag the release: `git tag v0.X.X && git push origin v0.X.X` - [ ] create GitHub release - [ ] final test install on `openpilot.comma.ai`