You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* re_web_viewer_server: be explicit with what gets bundled in the crate
* Fix a warning in release builds
* Publish the crates quietly to better follow their progress
* Update the RELEASES.md checklist
* Highlight all breaking changes
* Improve RELEASES.md
* Remove dead doctest
* Build-fix
Copy file name to clipboardexpand all lines: RELEASES.md
+24-14
Original file line number
Diff line number
Diff line change
@@ -40,34 +40,44 @@ Release builds of the Python Wheels are triggered by pushing a release tag to Gi
40
40
If we are doing a patch release, we do a branch off of the latest release tag (e.g. `v0.3.0`) and cherry-pick any fixes we want into that branch.
41
41
42
42
### Release checklist
43
-
Copy this checklist to the the PR description, go through it from top to bottom, and check each item before moving onto the next. This is a living document. Strive to improve it on each new release.
43
+
Go through this checklist from top to bottom, and check each item before moving onto the next.
44
+
This is a living document. Strive to improve it on each new release.
44
45
45
46
*[ ] Create a release branch called `release-0.x.y`
46
47
*[ ] If it is a patch release branch off `latest` and cherry-pick the commits that should be included
47
-
*[ ]For the draft PR description, add a:
48
-
*[ ]One-line summary of the release
48
+
*[ ]Update `CHANGELOG.md` with the new version number with:
49
+
*[ ]A one-line summary of the release
49
50
*[ ] A multi-line summary of the release
50
51
*[ ] A gif showing a major new feature
51
-
*[ ] Test the branch ([see below](#testing-a-release))
52
-
*[ ] Open the PR up for review with the `⛴ release` label
53
-
*[ ]`./scripts/publish_crates.sh --dry-run`
54
-
*[ ] Bump version number in root `Cargo.toml`.
55
-
*[ ] Update `CHANGELOG.md` with the new version number and the summary and the gif
56
52
*[ ] Run `pip install GitPython && scripts/generate_changelog.py`
57
53
*[ ] Edit PR descriptions/labels to improve the generated changelog
58
54
*[ ] Copy-paste the results into `CHANGELOG.md`.
59
55
*[ ] Editorialize the changelog if necessary
60
-
*[] Make sure the changelog includes instructions for handling any breaking changes
61
-
*[ ] Get the PR reviewed
56
+
*[] Make sure the changelog includes instructions for handling any breaking changes
57
+
*[ ] Commit and push the changelog
58
+
*[ ] Create a draft PR containing:
59
+
*[ ] One-line summary of the release
60
+
*[ ] A multi-line summary of the release
61
+
*[ ] A gif showing a major new feature
62
+
*[ ] Test the branch ([see below](#testing-a-release))
63
+
*[ ] Open the PR up for review with the `⛴ release` label
64
+
*[ ] Bump version number in root `Cargo.toml`.
62
65
*[ ] Check that CI is green
63
66
*[ ] Publish the crates (see below)
64
67
*[ ]`git tag -a v0.x.y -m 'Release 0.x.y - summary'`
65
68
*`git push --tags`
66
69
* This will trigger a PyPI release when pushed
67
-
*[ ]`git pull --tags && git tag -d latest && git tag -a latest -m 'Latest release' && git push --tags origin latest --force`
70
+
*[ ]`git pull --tags && git tag -d latest && git tag -a latest -m 'Latest release' && git push --tags origin latest --force`
71
+
*[ ] Manually trigger a new web viewer build and upload at https://github.com/rerun-io/rerun/actions/workflows/rust.yml
72
+
*[ ] Wait for CI to build release artifacts and publish them on GitHub and PyPI.
68
73
*[ ] Merge PR
69
-
*[ ] Wait for CI to build release artifacts and publish them on GitHub and PyPI. Verify this at https://github.com/rerun-io/rerun/releases/new.
74
+
*[ ] Edit the GitHub release at https://github.com/rerun-io/rerun/releases/edit/v0.x.0
75
+
*[ ] Mark it as as the latest release
76
+
*[ ] Paste in the `CHANGELOG.md`
77
+
*[ ] Wait for wheel to appear on https://pypi.org/project/rerun-sdk/
78
+
*[ ] Test the released Python and Rust libraries (see below)
70
79
*[ ] Wait for documentation to build: https://docs.rs/releases/queue
80
+
*[ ] Point <https://app.rerun.io/> to the latest release via instructions in <https://www.notion.so/rerunio/Ops-Notes-9232e436b80548a2b252c2312b4e4db6?pvs=4>.
71
81
*[ ] Post on:
72
82
*[ ] Community Discord
73
83
*[ ] Rerun Twitter
@@ -85,8 +95,8 @@ Before pushing the release tag:
85
95
*[ ] Mobile
86
96
87
97
After tagging and the CI has published:
88
-
*[ ] Test the Python packages from PyPI: `pip install rerun_sdk==0.3.0a1`
0 commit comments