(archive) Storage.01 release plan
Goals:
To release the RChain storage implementation as a separate library for use by Scala developers.
Done When:
Users can fetch the library as a JAR from Maven Central or build it from source.
Users can read Markdown documentation about how to use the library. This documentation will be published in the main {{rchain}} Github repository.
Users can read Scaladoc API documentation for the library. (TBD: where do we publish? GitHub Pages)
Users are able to store data into the library and retrieve the data by using the methods outlined in the documentation.
In more detail:
Out of Scope:
Storage functionality relating to history / blockdag / blockchain.
Operation in a distributed setting.
Support for system processes.
Tickets in the Milestone:
Project | Core |
|---|---|
Dev lead | @Henry Till |
Program lead | @Medha Parlikar (Unlicensed) |
Marketing lead | @Former user (Deleted) |
Status | in dev |
Start Date | Oct 9, 2017 |
Completion Date | Mar 29, 2018 |
Stakeholders
Name | Role | Reviewed |
|---|---|---|
@Lucius Meredith | CEO- CoOp | |
@Nash Foster | CEO- Pyrofex |
Dates to note
Milestone | Date | Notes |
|---|---|---|
Sprint 4 ends | Mar 9, 2018 | |
Sprint 5 ends | Mar 23, 2018 | |
Release from development | Mar 26, 2018 | Merge to master, build packages |
Membership demo | Mar 28, 2018 | |
Launch | Mar 29, 2018 | Public announcement |
Launch Readiness
Development
Description | Responsible | Status/Answer | Go/No Go |
|---|---|---|---|
Are we Code Complete | Dev Lead | typically Yes or no | |
Are all issues / tasks in the project marked as complete? | Program Lead | typically Yes or No, review issue list and obtain statuses on all items. | |
What is the test program | Dev/Test Lead | Describe the testing program (Create a page as part of this release for the testing program if needed) | |
| Dev Lead | Code needs to be in GitHub and under Continuous Integration. | |
Are there any known issues or limitations with the product? | Dev Lead | If yes, describe where the issues are documented | |
Are any of the issues potential blockers? | Dev Lead | If needed, review the open issues for the version in question. If issues exist, plan to fix or document. Reschedule the launch if needed. | |
How is the release packaged and installed? | Dev Lead | Describe how the release will be delivered to customers, how customers will install the package. (Maybe this needs to be a requirement specified up front.) | |
Have we shown the release to the membership? | Program Lead | Pre-release demo of the release should be given to the membership | |
Have we documented the release?
| Dev Lead/ Program Lead | Describe the technical documentation that will be delivered as part of the release. | |
Link to file issues | Program Manager | How will bugs against the release be tracked. Provide a link to file issues here. Also provide a link to query issues against the release here. |
Customer Facing Teams
Description | Responsible | Status / Answer | Go / No Go |
|---|---|---|---|
What is the Marketing Plan | Marketing | Provide a link to the marketing program, and indicate if all items are complete. | |
What is the Support Program | Program Lead | Describe how users will obtain support for the product. How will the support program be staffed, what is the SLA for support. | |
Documentation Program | Program Lead | Describe the external documentation plan. Provide a link if needed. How will the technical documentation be exposed to users. What format will the documentation take. | |
Metrics | Program Lead | Describe how the success of the release will be measured. What are the KPI's - these should map back to the goals of the release. How will the KPI's be collected and published. | |
Licensing | Program Lead | What license is the release licensed under? |