In this sprint, we focused on Refactoring Code to ensure our Load Testingwill go off without a hitch.
The list of changes includes:
- Load Testing
- 1 Node Test sending transactions to the network
- Multiple Nodes sending transactions simultaneously
- Various number of validator nodes across the network
- Different configuration for the nodes
- Unit Tests for Data Package
- Made changes to OneExplorer for handling data model fixes for OneLedger Protocol
- Finalized Lynx Architecture and Feature Set
In the next sprint, we are starting Lynx Engine Development, automating Explorer deployment and launching the Explorer on the updated protocol and generating an image for the cloud Marketplace.
NOTE: After the release for 0.9.0, we have reset the Chronos network and purging the current data. This is so that we can run more tests on Chronos and ensure it’s stability.
New Release Management Structure
OneLedger has a new release process. We will continue to update our Master Branch on GitHub on a bi-weekly basis. However, on a Quarterly basis, we will mark a build as a Release Candidate and work with our partners to ensure they update their nodes to the Protocol version for the most recent Release Candidate. This means Chronos will be updated on a quarterly basis.
We are doing this to streamline our release process and structure it for our partners and community. We are starting this process with version 0.9.0. For example, after v0.9.0, our next Chronos update will take place on v0.10.0, while we keep pushing the biweekly updates i.e. v0.9.1, v0.9.2 and so on.