-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Testnet checklist
- Notify DoubleZero Foundation of upcoming release (1 day patch, 2 days minor, 5 days major when possible)
- Deploy all components to devnet (daily all release includes QA) (trigger)
- PR version update in
Cargo.toml,Cargo.lock,CHANGELOG.md - Update versions in infra repo (example)
- Push tags for all components (plus a generic tag of 'v0.8.2') except client to trigger GH releases (trigger) and wait for releases to be published
- [SKIPPED - no smartcontract updates] Deploy serviceability and telemetry programs to configure version onchain instructions
- Deploy all components to testnet except the client - see system metrics dashboard (use "mode to run = send-it") (trigger)
- Confirm user-facing CLI backward compatibility with serviceability program
- Push tag for client to trigger GH release
- Wait for client to build and release
- Deploy our clients and onchain data collectors (trigger)
- QA connect/disconnect workflows via unicast and multicast with traffic flow on our client nodes (trigger)
- Validate onchain collector is publishing to influx
- Publish release notes (PR to
CHANGELOGin repo, update GH client/v0.8.2 release description) - Update recommended version in docs
- Post community announcement Slack/Discord - executed by foundation
internal templates here - Monitor dashboards for the next ~30 minutes watch for anomalies.
Mainnet-beta checklist
- Pause passport program and sentinel
- Upgrade passport program
- Resume passport program and sentinel
- Deploy serviceability and telemetry programs to configure version onchain
- Execute
doublezero init - Update pinned versions in ansible (example)
- Deploy components (
send-itmode) (trigger) - Deploy clients (
send-itmode) (trigger) - Run QA workflow (trigger)
- Check dashboards for any issues.
- Update recommended version in docs
Metadata
Metadata
Assignees
Labels
No labels