-
Notifications
You must be signed in to change notification settings - Fork 7
Closed
Milestone
Description
The v0.5.3 release of all components is scheduled for Tuesday August 19, along with deployment to testnet.
It will include client/v0.5.0...main. According to semver.org this should be a minor version release (0.6.0) because we added functionality in a backward compatible manner. However, the client currently treats a minor version update as breaking and won't let users use it without upgrading. So instead this is a patch version.
Checklist
- Notify DoubleZero Foundation of upcoming release (1 day patch, 2 days minor, 5 days major when possible)
- Deploy all components to devnet and QA (trigger)
- PR version update in
Cargo.toml - Push tags for all components (plus a generic tag of 'v0.5.3') except client to trigger GH releases
- Deploy all components to testnet except the client - see system metrics dashboard
- Deploy serviceability and telemetry programs to configure version onchain
- Execute
doublezero init - Confirm user-facing CLI backward compatibility with serviceability program
- Push tag for client to trigger GH release
- Deploy client to our own client nodes
- QA connect/disconnect workflows via unicast and multicast with traffic flow on our client nodes
- Update onchain collector to use new client version (nyc-tn-bm2)
- Validate onchain collector is publishing to influx
- Publish release notes (PR to
CHANGELOGin repo, update GH client release description) - Update client/v0.5.3 GH release description with the release notes
- Update client version in docs.malbeclabs.com setup: client version 0.4.0 docs#32
- Post community announcement Slack/Discord - executed by foundation
internal templates here
Versioned Components
- Activator
- Controller
- Client
- Funder
- Agent
- Device telemetry agent
- Internet latency collector
- Serviceability program
- Telemetry program
- Admin CLI
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels