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

Version 1 Next »

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
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 - at risk
  • Message chunking - on track, but Casper integration will likely roll over.
  • Interpeter hardening - coming along nicely, still at least 1 more sprint of work remains.
 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.
  • Client Interface ( CORE-1162 - Getting issue details... STATUS )
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
  • This is based off of story point estimates + velocity
  • January release would be updating of shard parameters + economics finalization.

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
    • 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.

Action items

  • No labels