mirror of
https://github.com/logos-messaging/logos-messaging-nim.git
synced 2026-02-21 06:13:11 +00:00
4.6 KiB
4.6 KiB
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Prepare Beta Release | Execute tasks for the creation and publishing of a new beta release | Prepare beta release 0.0.0 | beta-release |
Items to complete
All items below are to be completed by the owner of the given release.
-
Create release branch with major and minor only ( e.g. release/v0.X ) if it doesn't exist.
-
Assign release candidate tag to the release branch HEAD (e.g.
v0.X.0-beta-rc.0,v0.X.0-beta-rc.1, ...v0.X.0-beta-rc.N). -
Generate and edit release notes in CHANGELOG.md.
-
Validation of release candidate
- Automated testing
- Ensure all the unit tests (specifically logos-messaging-js tests) are green against the release candidate.
- Waku fleet testing
- Deploy the release candidate to
waku.testthrough deploy-waku-test job and wait for it to finish (Jenkins access required; ask the infra team if you don't have it).- After completion, disable fleet so that daily CI does not override your release candidate.
- Verify at https://fleets.waku.org/ that the fleet is locked to the release candidate image.
- Confirm the container image exists on Harbor.
- Search Kibana logs from the previous month (since the last release was deployed) for possible crashes or errors in
waku.test.- Set time range to "Last 30 days" (or since last release).
- Most relevant search query:
(fleet: "waku.test" AND message: "SIGSEGV"),(fleet: "waku.test" AND message: "exception"),(fleet: "waku.test" AND message: "error"). - Document any crashes or errors found.
- If
waku.testvalidation is successful, deploy towaku.sandboxusing the deploy-waku-sandbox job. - Search Kibana logs for
waku.sandbox:(fleet: "waku.sandbox" AND message: "SIGSEGV"),(fleet: "waku.sandbox" AND message: "exception"),(fleet: "waku.sandbox" AND message: "error"). most probably if there are no crashes or errors inwaku.test, there will be no crashes or errors inwaku.sandbox. - Enable the
waku.testfleet again to resume auto-deployment of the latestmastercommit.
- Deploy the release candidate to
- Automated testing
-
Proceed with release
- Assign a final release tag (
v0.X.0-beta) to the same commit that contains the validated release-candidate tag (e.g.v0.X.0-beta-rc.N) and submit a PR from the release branch tomaster. - Update logos-delivery-compose and logos-delivery-simulator according to the new release.
- Bump logos-delivery dependency in logos-delivery-rust-bindings and make sure all examples and tests work.
- Bump logos-delivery dependency in logos-delivery-go-bindings and make sure all tests work.
- Create GitHub release (https://github.com/logos-messaging/logos-delivery/releases).
- Submit a PR to merge the release branch back to
master. Make sure you use the option "Merge pull request (Create a merge commit)" to perform the merge. Ping repo admin if this option is not available.
- Assign a final release tag (
-
Promote release to fleets
- Ask the PM lead to announce the release.
- Update infra config with any deprecated arguments or changed options.
- Update waku.sandbox with this deployment job.