...
Iroha 2 is ramping up production. All developers are now fully onboarded and at maximum productivity. We have implemented a crude delineation of responsibilities, and implemented all processes for long-term development. We are following a timed release cadence, with a Long-term supported release planned at critical stability milestones. Iroha 2 repository is well organised, with branch protection rules enforced for all main branches (iroha2-stable
, iroha2-dev
, iroha2-lts
, iroha2-staging
) as well as a common CI/CD pipeline with thorough testing/linting and API verfication systemsverification systems.
Work is underway to bring the supporting libraries up to feature parity with the Rust library. Particular efforts are made to improve the Iroha Python library to be available for testing and automation. Additionally, a Hyperledger Cactus plugin is developed based on the Iroha typescript library. Additional tooling is made for improving the UX, and the Blockchain explorer is nearing the minimum viable product state. Finally, Iroha Kotlin is going to be used as a basis for a public test network, where we will analyse real-world usage statistics and use the data-driven optimisation approaches optimisation approaches to further improve Iroha 2.
...
We have a few issues in relation to Hyperledger Ursa. For example, due to its release cadence and relative lull in development activity, we had had to hold back a few dependencies in order to remain binary compatible with the Errors
returned from Ursa methods. Our automated auditing tools have identified several deprecations as well as unmaintained libraries which cannot be simply “version bumped” into Ursa.
...
Last release reported here at May 26, 2022.
Timed releases:
v2.0.0-pre-rc.4
(internal)v2.0.0-pre-rc.5
(internal)v2.0.0-pre-rc.6 (LTS)
v2.0.0-pre-rc.7
(internal, TBR)
...
- #2494: Update documentation: AddPeer with
syncing_node
option - #2475: Many documentation changes, corrections, etc.
...
Based off of that we triggered a series of simplifications and optimisations which led to increased performance in the iroha2-staging
branch. It is our best bet to increase throughput.
...
- 8 Rust developers + 1 tech lead
- 1 front-end developer
- 2 full-time QA engineers (functional and load testing/benchmarking)
- 1 full-time technical writer
- 1 full-time DevOps
- 1 community manager, who also handles front-end, back-end, DevOps and writing tasks as needed
Currently, the maintainer team consists of the Soramitsu employees. Gregorz Bazior (Yonix Digital Systems, AGH University of Science and Technology) is interested in Iroha 2 and maintains Iroha 1.
Contributor Diversity
A new intern working on reimplementing iroha-swarm as a plugin to Kagami (Iroha 2’s example generation program).
We have had several contributions (#2264, #2285, #2326) from Omkar Mohanty (intern), Tejas (intern), who has shown interest, but has not contributed code directly and Ritik Bhandari who contributed the code that was part of PR#2125 (add query for FindAssetDefinitionById
).
On the Python side of Iroha, we’ve had valuable input about ergonomics of the Iroha 2 Python library from Gregorz Bazior (Yonix Digital Systems, AGH University of Science and Technology).
Reviewed By
- Angelo De Caro
- Arnaud J Le Hors
- Artem Barger
- Arun S M
- Bobbi Muscara
- Danno Ferrin
- David Enyeart
- Grace Hartley
- Jim Zhang
- Kamlesh Nagware
- Nathan George
- Peter Somogyvari
- Tracy Kuhrt
- Troy Ronda
Submission date
18-Aug-2022, added the review section at 1-Sep-2022