Reference
Document status |
| ||||||
Release status |
|
Milestones
Start date |
|
Release |
Stakeholders
CTO | ||
CEO |
Development team
Program manager | Project Manager | Engineering Lead | SRE |
Release Overview
Simple Overview
With 20.08 Release, we have delivered a functional Rust implementation that can stand up a XX (minimum 20) node network for at least 7 days. The network would include implementation of economics (Seigniorage only) and Era rotation, Bonding and Unbonding with bonding auctions.
Nodes can join the network and sync with the rest of the nodes to catch up on state transitions. Validator set rotation happens at the junction of eras. A fixed maximum number of slots is available that is capped at 50 nodes. (Note we need to know that the network is stable at the maximum cap -since anyone can join).
Seigniorage will be given to validators for participating in consensus.
Work on the Rust implementation
20.08 Release will include:
Ability to stand up a XX (minimum 20) node network for at least 7 days. [limiting to 5 to 10 nodes. Stretch goal of 20 nodes].
The network would include implementation of economics (Seigniorage ) but no slashing or liveness penalty
Era rotation
Rust Node
Evolving Rust client
Consensus Component implementation [stretch or partial goal]
STest updates to work with the new Rust Node
Ecosystem Product Updates
Metrics in Clarity
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Release Contract macros
Can’t find any tickets for this.
Update Signer
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Solidity toolchain
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Gitpod online IDE Implementation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
New CL Blog site
Need to find this
Move Clarity to a Separate Repo
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
SRE
Metrics
Work to support Testnet
Address issues discovered in the Testnet.
Fixes to stabilize Testnet.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Tickets for this Release
Features
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Defects Fixed
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Metric for tracking the success:
What is special about this release?
For dApp Developers
For Node Operators
Are we doing something differently? If so, why are we doing it this way?
Before these features were available, what were developers able to do?
After these features launch, what will developers be able (and not able) to do?
Description of release packaging
Release packaging will include:
Debian package
Docker image
Brew packages
RPM package
tar.gz file
Where do developers go to learn more and get started?
At release, links to installation packages and relevant documentation is available at
Packages available at: http://github.com/CasperLabs/releases
Docs available on GitHub.
Where will bugs be filed?
Github - part of the public release.
Where do developers go for support? What is the SLA? Who is on point?
Gitter developer channel