Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Date

Attendees

Goals

  • Review  Node 7 - status on release readiness
  • Review Node 8 Scope
  • Rolled over items
    • Discuss RSong demo learnings
    • Discuss Client experience

Discussion items

TimeItemWhoNotes

Mercury release plan
  • Work in progress
  • Mercury release plan - please review.
    • Node team is working on updates this week
    • Suggestion that the plan should be user-focused (deliverable features) rather than specification or implementation details
    • Rita is available to pair with Pawel to walk through Mercury deliverables. Pawel Szulc (Unlicensed) please coordinate with Rita to find a time for this walkthrough
5 minutes

node-0.7 release plan   

  • 10/15 (Testnet)     
Medha Parlikar (Unlicensed)
  • Name Registry - Done
    • Porting of Contracts will roll over.
    • Removing the ability to listen on forgeable names will be on hold until contracts are ported.
  • Validator Bonding - Done
    • Includes Faucet contract - to support bonding with Rev
  • Cost Accounting
  • Threading - needs testing & integration with the other teams.  Likely rolling over.
    • Partial or complete (depending on testing in progress this week) implementation with completion of CORE-1230 that should be complete for RNode v0.7
    • When done, this work should improve the stability of the node.
    • Next step, when PR for CORE-1230 is complete idea to add flags for every aspect addressed in CORE-1230 TICKET NEEDED
  • Message chunking - on track, but Casper integration will likely roll over.
  • Interpreter hardening - coming along nicely, still at least 1 more sprint of work remains.
  • Test net refresh to take place 10/15 per the plan described in 2018-10-02 Meeting notes: release planning and test net updates
 10 minutes

node-0.8 release plan

  • 11/12 (Testnet)
 Medha Parlikar (Unlicensed)
  • Testnet Faucet
    • Jack Mills will build a generic web service that will talk to the faucet & return data. 
  • Storage
    • Storage shards only.  We do not have time to do anything else.
    • Will this support royalty contracts?
      • Storage shards have all of the requirements of a general shard. As such, there is support for getting royalties off this shard
      • Concern this is sub-optimal for users who would have to get currency off the storage shard, and move it to the root shard. This creates an over-head cost for the user.
  • Client Interface ( CORE-1162 - Getting issue details... STATUS )
    • Discussion on what this is and why it's needed
    • Meeting planned for 10/4 with Pawel, Mike Stay, and Kent to discuss this ticket and plan for work needed
10 minutes

node-0.9 release plan

  •  12/10 (Testnet)
Medha Parlikar (Unlicensed)
  • Sharding client software
    • Request for team to review Shards in RChain
    • Kyle projects 4 sprints to get this done.
    • Registry took longer to complete.
  • Lazy Validator Hedge
  • Governance outcomes - Economics

Dev Done dateMedha Parlikar (Unlicensed)
  • Jira shows me end of January
    • Medha showed a graph from Jira showing a projection of feature complete in Jan.
  • This is based off of story point estimates + velocity
  • January release would be updating of shard parameters + economics finalization.
  • Requirement to release in Q1 relates to contractual obligations between the Coop and Pithia
  • Extra-protocol sharding must precede in-protocol (level II) sharding 
    • Question of when which gets delivered when
  • Idea to consider working with 3rd party to support open work items
    • See action items below for next steps
  • Idea to hire production developer to support testing of features. Michael Stay (Unlicensed) to follow up.

Performance of the system
  • Concerned about the following items relating to performance
    • Our Grafana dashboards are still not working after the switch of how we report metrics. Medha Parlikar (Unlicensed) confirm this is ticketed so it can be done next sprint.
    • We don't have baselines yet for performance that are socialized amongst the team
    • We don't have a person or team in charge of performance.  Yet this is the most important deliverable we have.
    • CORE-1054 - Getting issue details... STATUS

Action items

  • No labels