A view of the issues blocking launch of a public test net is available here.
Platform stability is priority #1 for most people on the team.
Mercury requirements and acceptance criteria
The development team has work this sprint to support the creation of test cases and acceptance criteria for stories that are ready. A view of this work is available here.
User story requirements, testing scenarios, and status will be reported in features.md. This is a work in progress. When complete stakeholders will have a web-based dashboard showing the requirements and the status of the acceptance criteria.
Work with Whiteblock
In progress. Received documentation and collaborating with the Whiteblock team.
Dev team members planning some small time off over the Christmas and New Year's holidays. With few exceptions, this team has not had approved vacation since Nov. 2017. We're still operating on that model to support Mercury delivery.
Current sprint ends Dec. 24. Next sprint will start Jan. 2. Those who plan to work between sprints have a clear backlog.
No community RNode testing Dec. 25 or Jan. 1. We'll resume on Jan. 8.
Block store work should be complete by end of week. Recent work is to assure integration tests pass with the implementation of the new store.
In support of stability work, work in progress to improve the output messaging of Rholang unit tests to be more explicit about causes of failures.
In addition to supporting stability work, working on other bugs and continuing work on the block store.
Fully focused on stability work.
Work in progress to remove deploys from finalized blocks to help node not run out of memory.
Investigation of the issue of node hanging on propose.
PR merging today to implement a new metrics API, CORE-1489.
Add Kamon InfluxDB reporter
Add command-line flags and configuration options for Prometheus and InfluxDB reporters
Change Metrics-API to take an implicit MetricsSource parameter with a module name
Use node-id as metrics hierarchy root name
Review existing metrics if they make sense and are required
Add new metrics if required
Use Kamon System Metrics instead of our own JVM metrics
Use histograms instead of gauges
Implement a timer in Metrics
Priority is stability work.
Priority is stability work: improvements to test infrastructure and work to make use of the new metrics API to improve monitoring and reporting,