-
Notifications
You must be signed in to change notification settings - Fork 9
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& merge to main - Update versions in infra repo (example)
- Push tags for all components except client to trigger GH releases (trigger) and wait for releases to be published
- Deploy serviceability, telemetry, and geolocation programs to configure version onchain instructions
- Check CloudSmith latest release (link)
- Deploy all components to testnet except the client - see system metrics dashboard (use "mode to run = send-it") (trigger)
- Deploy our clients and onchain data collectors (trigger)
- QA connect/disconnect workflows via unicast and multicast with traffic flow on our client nodes (trigger)
- 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
- Promote component packages from cloudsmith doublezero-testnet repo to doublezero repo (trigger)
- Deploy telemetry (first) and serviceability programs to configure version onchain
- Execute
doublezero init - Promote client packages from cloudsmith doublezero-testnet repo to doublezero repo (trigger)
- 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.
- Check recommended version in docs
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels