Versions Compared

Old Version 7

changes.mady.by.user Piotr Dziubecki

Saved on

compared with

New Version Current

changes.mady.by.user Piotr Dziubecki

Saved on

Key

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

Reference

Document status

Status
colourYellow
titleDRAFT

Release status

Status
colourBlue
titlePLanning

Milestones

Start date

 

Release branch cut (1.2.0)

Testnet upgrade

Stage Mainnet upgrade (1.2.0)

Stakeholders

Ralf Kubli

CTO

  •   

CEO

  •   

Development team

Program manager

Project Manager

Engineering Lead

SRE

Medha Parlikar

Piotr Dziubecki

Ed Hastings (Deactivated)

Joe Sacher


Marketing team

Marketing lead

Content owner

Matthew Iles (Unlicensed)

Everett M (Unlicensed)


Release Overview

Simple Overview

Release 21.05 marks the second Mainnet version upgrade of the Casper protocol. The team has identified several areas of opportunity where the protocol will benefit from performance and sustainability fixes.

Detailed Overview

This release will focus on Performance & Sustainability.

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

  • Context state improvements

  • Network stability enhancements

  • Deploy processing stabilization

  • Event stream enhancementenhancements

  • Update documentation at docs.casperlabs.io

Node

  • Network stability enhancements

  • Deploy processing stabilization

  • Event stream enhancement

Execution Engine

  • Context state improvements

  • Quantstamp audit remediation Make bottom third of auction contract participants a rotating set (randomize it according to stake).

Ecosystem

  • JS SDK release with a new implementation of CLValue

  • Casper Signer with support for mnemonics and integration tutorial

  • The first release of Caspiler

  • The new version of the vesting contract

  • Update documentation at docs.casperlabs.io

  • 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.05) 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.05 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.05"
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.05
serverId74adbfdc-03f9-334e-80a4-d9a3f2a98ccf

Key Contract Runtime Deliverables

Jira Legacy
serverSystem JIRA
maximumIssues1000
columnskey,summary,status,sprint,priority
jqlQueryproject = ee and fixVersion = 21.05
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.05
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.05 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?