Created by Sara Garifullina, last modified by Kelly M Olson on Apr 18, 2019
During the last several months we released several Release Candidates, tested them and prepared Iroha’s performance for the v1.0 release.
- Significantly reduced memory consumption
- Implemented load tests
- Moved to native client libraries
- Implemented peer interaction testing framework
- Performance improvements
Regarding the load tests, we have been using machines generously provided by CNCF https://github.com/cncf/cluster/issues/109 .
We received approval from TSC to move to v1.0! Community is active, questions are asked and answered. We’ve also got in contact with different developers after HK Bootcamp and very excited for the future contacts with them.
We also have our own weekly call now! Join us every Wednesday at 10am GMT.
Still have DCO issue that is blocking the release. Diversity is not enough.
Hyperledger Iroha v1.0 Release Candidate 3 - on February, 11th
Hyperledger Iroha v1.0 Release Candidate 4 - on March, 1st
Hyperledger Iroha v1.0 Release Candidate 4 Hotfix 1 version - on March, 5th
Hyperledger Iroha v1.0 Release Candidate 5 - on March, 21st
We had some active discussions regarding the release with active members of the HL community. Our maintainer attended HK Bootcamp and through that we’ve met HK HL Community and are having a remote meetup with them in a week, on April 24. Questions are being replied to in chats so more people could use Iroha in their work. We receive many questions about SDKs nowadays.
We also fixed DCO issue that was blocking the release of 1.0 and had a HL Iroha meetup in Tokyo!
Release the production-ready version is a #1 goal for the team at the moment. We hope it will bring us new users and new contributors, make our community stronger. Projects built on Iroha are also being released into production. The plan for the nearest future is to make Iroha fully BFT and then start working on custom commands. Moreover, the following features are planned: include support for Ursa library, improve the granularity of permission model, introduce TLS node-node and client-node encryption, support for consistent network-wide configuration parameters stored in the ledger, stateful validation of genesis block, statistics API.
No changes were made though we will be changing the maintainers list after the release, clarifying some rules for becoming a maintainer, which might help us diversify the community.
Contributors are still mainly Soramitsu employees and some individual contributors also help us (for example, with translations).
After 1.0 we hope to diversify the community of contributors as well.
Updates since the last report:
Documentation and translation
Ivan ( email@example.com ) Spanish
Vadim ( firstname.lastname@example.org ) Russian
Mercedes Regueiro ( email@example.com ) Spanish
Zhenhua Zhao ( firstname.lastname@example.org ) Chinese (simplified)
Yang Cheng ( email@example.com ) Chinese (simplified)
Caozhao ( firstname.lastname@example.org ) Chinese (simplified)
Resetarsi ( email@example.com ) Korean
pikatos ( firstname.lastname@example.org ) French
Lira.lemur ( email@example.com ) Russian
Commits from 2019-01-23 to 2019-04-15: 139
Committers from 2019-01-23 to 2019-04-15: 19
Domains from 2019-01-23 to 2019-04-15: 8
- ✅ Arnaud Le Hors
- ✅ Baohua Yang
- ✅ Binh Nguyen
- ✅ Christopher Ferris
- ✅ Dan Middleton
- ✅ Hart Montgomery
- ✅ Kelly Olson
- ✅ Mark Wagner
- ✅ Mic Bowman
- ✅ Nathan George
- ✅ Silas Davis
Do you feel you have an effective plan in place to resolve the DCO issues? Who in Iroha is responsible for resolving and who is responsible at HL for verifying?
Posted by firstname.lastname@example.org at Apr 18, 2019 12:56
It was already resolved with the help of Ry and David from HL's side.
Posted by SaraG at Apr 18, 2019 13:04
I have helped to resolve it recently: https://github.com/hyperledger/iroha/commit/6c77597ab55163667931591e774f6a04d91b403b
Posted by lebdron at Apr 18, 2019 13:18