| | | |
|---|
| Mercury release plan |
| |
5 minutes | node-0.7 release plan | @Medha Parlikar (Unlicensed) | Name Registry - Done Validator Bonding - Done 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 | RNode-0.8.1 release plan | @Medha Parlikar (Unlicensed) | |
10 minutes | node-0.9 release plan | @Medha Parlikar (Unlicensed) | |
| Dev Done date | @Medha 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. Requirement to release in Q1 relates to contractual obligations between the Coop and Pithia Extra-protocol sharding must precede in-protocol (level II) sharding Idea to consider working with 3rd party to support open work items Idea to hire production developer to support testing of features. @Michael Stay (Unlicensed) to follow up.
|
| Performance of the system |
| |