Node X.Y Release Plan Template
Reference
Document status | NOT STARTED |
Release status | NOT STARTED |
Related pages |
Milestones
Start date | |
Sprint # | |
| Sprint # | |
Release |
Stakeholders
Name | Role | Reviewed? |
| Medha Parlikar | CEO, CasperLabs | |
| Mrinal Manohar | CEO, ADAPtive |
Development team
Program manager | Project manager | Developer | Developer | Developer | SRE |
| Ashok Ranadive | Rita Allen | Michael Birch | Akosh Farkas | Henry Till | Tom Vasile |
Marketing team
Marketing lead | Content owner |
| TBD | TBD |
Release Overview
Simple Overview
Detailed Overview
Clarity
Node Features
Execution Engine Features
Consensus Features
Storage Features
Operations
EcoSystem
Metric for tracking the success:
What is special about this release?
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:
- Docker image (Supported on Linux only)
- Debian package
- 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