User Tools

Site Tools


groups:tsc:project-updates:iroha-2018-oct

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

groups:tsc:project-updates:iroha-2018-oct [2018/10/22 16:05]
Sara Garifullina created
groups:tsc:project-updates:iroha-2018-oct [2018/10/22 17:04] (current)
Sara Garifullina
Line 5: Line 5:
  
 ===== Project Health ===== ===== Project Health =====
-Within the period after the previous report we were working on stability, optimisations,​ and new features. Community manager ​responds to everyone ​in Iroha community chats in Rocketchat, telegram and gitter. \\ Community has been very active and helped us in finding bugs and problems in develop version of Iroha. That issues made us to postpone next release, which will be shipped in the coming week. We keep community updated with the statuses of the bugs that they find.+Within the period after the previous report we were working on stability, optimisations,​ and new features. Community manager ​makes sure all questions ​in Iroha community chats in Rocketchat, telegram and gitter ​get responded. \\ Community has been very active and helped us in finding bugs and problems in develop version of Iroha. That issues made us to postpone next release, which will be shipped in the coming week. We keep community updated with the statuses of the bugs that they find.
  
  
Line 13: Line 13:
  
 ===== Releases ===== ===== Releases =====
-Next week Hyperledger Iroha v1.0 beta-version ​will be shipped. It will include ​performance improvements,​ critical reliability bug fixes and API changes. ​The final release is planned for the end of Q4 2018.+We have had 1 release and now the latest version is Hyperledger Iroha v1.0 beta-version, released on 2nd of August\\ 
 +It included ​performance improvements,​ critical reliability bug fixes and API changes. ​ 
  
  
 ===== Overall Activity in the Past Quarter ===== ===== Overall Activity in the Past Quarter =====
 In Iroha, communication mostly takes place in chats rather than mailing lists. Most of the questions get responded to within few hours or less (with an exception when a message gets lost in the chat among several messages). Currently we actively use 1 chat channel (#Iroha). We launched telegram channel for Iroha News in order to be up to date with Iroha updates. Some important changes to Iroha are accompanied with online webinars, where any community member can participate and ask any questions to developers online. \\ \\ In Iroha, communication mostly takes place in chats rather than mailing lists. Most of the questions get responded to within few hours or less (with an exception when a message gets lost in the chat among several messages). Currently we actively use 1 chat channel (#Iroha). We launched telegram channel for Iroha News in order to be up to date with Iroha updates. Some important changes to Iroha are accompanied with online webinars, where any community member can participate and ask any questions to developers online. \\ \\
-Past Quarter has been mostly devoted for refactoring and optimisations in Iroha, which led to higher transactions throughput and less compilation time. We also added new features, such as GetRolePermissions query, Iroha health check, and more thorough Query Error messages. We fixed bugs related to synchronisation mechanism in Iroha. Our community helped us with early bug reports. \\ \\ The remaining scope for the final release in December 2018 includes: \\ +Past Quarter has been mostly devoted for refactoring and optimisations in Iroha, which led to higher transactions throughput and less compilation time. We also added new features, such as GetRolePermissions query, Iroha health check, and more thorough Query Error messages. We fixed bugs related to synchronisation mechanism in Iroha. Our community helped us with early bug reports. \\ 
-  * Network testing Framework \\ +
-  * Byzantine Fault Tolerant ordering service \\ +
-  * YAC consensus documentation and experiments \\ +
-  * Peer initialization \\ +
-  * Log queries errors to an output of peers \\ +
-  * Replay attacks solution for queries and transactions \\ +
-  * Implementation of reject case in YAC consensus — as soon as empty blocks are not written in the ledger \\ +
-  * Iroha online sandbox \\ +
-  * Load testing and performance regressions (preferably on Hyperledger Caliper)+
  
  
Line 37: Line 30:
 4. Increase diversity of maintainers \\ 4. Increase diversity of maintainers \\
 5. Move to Hyperledger Jira from Soramitsu’s Jira \\ 5. Move to Hyperledger Jira from Soramitsu’s Jira \\
 +
 +The remaining scope for the final release in December 2018 includes: \\
 +  * Network testing Framework \\
 +  * Byzantine Fault Tolerant ordering service \\
 +  * YAC consensus documentation and experiments \\
 +  * Peer initialization \\
 +  * Log queries errors to an output of peers \\
 +  * Replay attacks solution for queries and transactions \\
 +  * Implementation of reject case in YAC consensus — as soon as empty blocks are not written in the ledger \\
 +  * Iroha online sandbox \\
 +  * Load testing and performance regressions (preferably on Hyperledger Caliper)
  
  
groups/tsc/project-updates/iroha-2018-oct.txt · Last modified: 2018/10/22 17:04 by Sara Garifullina