Mercury
Reference
| Document status | PLANNING |
|---|---|
| Release status | NOT STARTED |
| Related pages | RChain wiki |
Action items
- Michael Stay (Unlicensed) complete the release summary section of this document.
Milestones
| Start date | |
|---|---|
| Sprint | date |
| Sprint | date |
| Release from development | date |
| Membership demo | date |
| Release | date |
Development team
| Development lead | Program manager | Project manager | Developer | Developer | DevOps | Page owner |
|---|---|---|---|---|---|---|
| Michael Stay (Unlicensed) | Medha Parlikar (Unlicensed) | Jeremy Busk | Medha Parlikar (Unlicensed) |
Stakeholders
| Name | Role | Reviewed? |
|---|---|---|
| Lucius Meredith | CEO - RChain coop | |
| Nash Foster | CEO - Pyrofex |
Marketing team
| Marketing lead | Evangelist | Content owner |
|---|---|---|
| Lawrence Lerner |
Release summary
Simple overview
This release implements wallet contracts on the RChain blockchain.
Technical overview
Metric for tracking success
Done when:
- Example wallet contract is operating on blockchain.
- Tested to transaction rates of at least 500 transactions / second.
- Release readiness complete.
- All tests pass.
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 with RChain?
After these features launch, what will developers be able (and not able) to do with RChain?
Description of release packaging
Where do developers go to learn more and get started?
Where will bugs be filed?
Where do developers go for support? What is the SLA? Who is on point?
What license will this be released under?
Release goals
| # | Description | Notes | Issue created in JIRA? |
|---|---|---|---|
| 1 | Validation of code completeness | ||
| 2 | Validation of merge to master (prior to packaging) | ||
| 3 | Validation of issue completion | ||
| 4 | Prepare and deliver demo to membership | ||
| 5 |
JIRA issues in this release
Coming soon