In our last sprint, we focused on the Wallet, Chain Driver, Build Automationand some technical debt.
The list of changes includes:
- Chain Driver Engine: Implement RPC call for Ethereum
- Optimized P2P connection for Validator Nodes
- Setup Ansible for Devnet
- Setup Terraform for Devnet on GCP
- Re-evaluate Serialization methodology for Golang
- data.Coin.String() was printing 0 when the currency was set to OLT
- On-Boarding Flow: Generate mnemonic words from JS Library
In the next sprint, we will still be working on some tech debt, specifically on our serialization methodology and we will begin preparations for load testing our network.
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.