Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Reference

Document status

Status
colourGreen
titleCOMPLETE

Release status

Status
colourGreen
titlein Dev

Milestones

Start date

 

Release branch cut

 

Testnet upgrade

Stage Mainnet upgrade (1.1.0)

Stakeholders

Development team

Program manager

Project Manager

Engineering Lead

SRE

Medha Parlikar

Piotr Dziubecki

Ed Hastings (Deactivated)

Joe Sacher


Marketing team


Release Overview

Simple Overview

Release 21.04 marks the first Mainnet version upgrade of the Casper protocol.

The most important thing is to launch Mainnet and keep it up and stable.

Detailed Overview

This release will focus on Performance & Sustainability.

The goal is to patch Mainnet with the first round of sustainability features:

  • Reduce Protocol State Memory Consumption

  • Networking Robustness

Protocol Features:

  • Make it very hard to equivocate in Casper node.

Node

  • Network stability

  • Joiner reliability

Operations & Monitoring

  • Transition to casper-network

  • Implement production monitoring and production lead process for Mainnet.

  • Enhance Nightly Infra & tests - better simulate the live network.

  • Tutorials and videos on metrics and monitoring

Ecosystem

  • Update documentation at docs.casperlabs.io

  • JavaScript SDK enhancements

  • Signer enhancements

  • Smart Contract DSL enhancements

  • Developer experience courses

  • Video tutorial content for the following

    • setting up a node

Tickets for this Release

Features

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,status,priority
jqlQueryproject = FEAT and fixVersion in(21.04) AND ( labels not in ("ecosystem") or labels is EMPTY) or (project = FEAT and fixVersion is EMPTY and status in ("Implementing", "In review") AND ( labels not in ("ecosystem") or labels is EMPTY)) ORDER BY priority
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Ecosystem Features

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,status,priority
jqlQueryproject = FEAT AND issuetype = Epic AND status in (Analyzing, Backlog, Implementing, "In Review", Planning) AND fixVersion = 21.04 AND labels =ecosystem or (project = FEAT and fixVersion is EMPTY and status in ("Implementing", "In review") and labels in ("ecosystem"))ORDER BY priority
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Consensus Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues20
columnskey,summary,assignee,status,sprint,priority
jqlQueryIssuetype=story and labels ="consensuscrew" and fixVersion="21.04"
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Node Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues1000
columnskey,summary,assignee,status,sprint,priority
jqlQueryissuetype !=Epic and project=node-rs and FixVersion=21.04 and labels is empty
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Contract Runtime Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues1000
columnskey,summary,status,sprint,priority
jqlQueryproject = ee and fixVersion = 21.03 04
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Ecosystem Product Updates

  • Javascript SDK

  • Enhancements to Signer

Jira Legacy
serverSystem JIRA
maximumIssues1000
columnskey,summary,assignee,status,sprint,priority
jqlQueryproject = eco and FixVersion = 21.04
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

SRE

  • Network Health Monitoring

Documentation

  • Updated dApp developer guide for Rust Node

Defects Fixed

Jira Legacy
serverSystem JIRA
columnskey,summary,status
maximumIssues1000
jqlQueryissuetype = Bug AND fixVersion= 21.04 ORDER BY status DESC, key ASC
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

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. http://docs.casperlabs.io

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?