-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Fabric 2023 Q3 report. Signed-off-by: David Enyeart <[email protected]>
- Loading branch information
Showing
1 changed file
with
88 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
--- | ||
layout: default | ||
title: 2023 Q3 Hyperledger Fabric | ||
parent: 2023 | ||
grand_parent: Project Updates | ||
has_children: false | ||
has_toc: false | ||
--- | ||
|
||
# 2023 Q3 Hyperledger Fabric | ||
|
||
# Project Health | ||
|
||
Hyperledger Fabric is fairly mature and stable with a v2.5 Long-term support (LTS) release. | ||
There is less churn and fewer commits than in years past, with continued focus on quality and support. | ||
New features get proposed, approved, and implemented based on a community RFC process. | ||
Mailing list activity is down a bit compared to prior years. | ||
PRs and mailing list questions are generally turned around quickly. | ||
There is significant Discord activity. | ||
|
||
# Questions/Issues for the TOC | ||
|
||
None. | ||
|
||
# Releases | ||
|
||
LTS releases: | ||
- v2.5 is the current LTS release with patch releases approximately quarterly. | ||
- v2.2 is the prior LTS releases, critical fixes will be backported through 2023. | ||
|
||
The Fabric [v2.5 announcement](https://lists.hyperledger.org/g/fabric/message/11754) encouraged users to upgrade to v2.5 so that they can keep getting fixes and updates that will eventually be targeted for v2.5.x releases only. | ||
The announcement also indicated that the legacy Fabric SDKs (known as Fabric SDK for Node v2.2, Fabric SDK for Java v2.2, Fabric SDK for Go v1.0) are deprecated. | ||
Users of the legacy SDKs are encouraged to evaluate the Fabric Gateway client API as a replacement. | ||
The Fabric Gateway client API is the recommended SDK for client applications when using Fabric v2.4 or v2.5, and is available in Go, Node, and Java programming languages. | ||
|
||
[Releases](https://github.com/hyperledger/fabric/releases) past quarter: | ||
|
||
- Fabric v2.2.11 - April 21, 2023 | ||
- Fabric v2.2.12 - June 2, 2023 | ||
- Fabric v2.5.1 - May 1, 2023 | ||
- Fabric v2.5.2 - June 2, 2023 | ||
- Fabric v2.5.3 - June 14, 2023 | ||
|
||
# Overall Activity in the Past Quarter | ||
|
||
The project delivered fixes to the Fabric v2.2 (prior LTS) and v2.5 (current LTS) releases. See [release notes](https://github.com/hyperledger/fabric/releases) for details. | ||
|
||
SmartBFT consensus algorithm has been integrated into the Fabric ordering service (main branch). Samples and documentation are being prepared for a Fabric v3.0 preview release. | ||
|
||
An initial v0.0.0 of Go [fabric-admin-sdk](https://github.com/hyperledger/fabric-admin-sdk) has been released to help with programatic channel and chaincode management. | ||
The project is evaluating the use of this admin SDK in a new and improved [fabric-cli](https://github.com/hyperledger/fabric-cli) that may eventually replace the original peer CLI commands. | ||
|
||
Project members are helping to draft exam questions for the upcoming Hyperledger Fabric Certified Practitioner exam. | ||
|
||
# Current Plans | ||
|
||
The project expects to maintain and support v2.5 for an extended time period | ||
and encourages all users to upgrade to v2.5 so that they can keep getting fixes that will eventually be targeted for v2.5 only. | ||
|
||
The project intends to release a `v3.0.0-preview` release so that users can try out the initial SmartBFT feature, this will be Fabric's first Byzantine Fault Tolerant (BFT) consensus algorithm. | ||
The plan is to get feedback on the SmartBFT feature, and also refactor the ordering service | ||
so that there will be one orderer binary per consensus algorithm, which will be much more | ||
extensible than the current approach of having one orderer binary that supports N consensus algorithms. | ||
The project intends to refactor other code as well in an eventual v3.0 release, | ||
and also remove some of the heritage features that have already been announced as deprecated in the [v2.x release notes](https://github.com/hyperledger/fabric/releases/tag/v2.5.0). | ||
The refactoring work will take significant time, therefore most users are encouraged to use v2.5 which will be maintained and supported for an extended time period. | ||
|
||
# Maintainer Diversity | ||
|
||
7 of 8 [maintainers](https://github.com/hyperledger/fabric/blob/main/MAINTAINERS.md) from IBM. | ||
|
||
The project maintainers are working with the Hyperledger staff to identify and mentor new contributors and maintainers to increase diversity. | ||
|
||
# Contributor Diversity | ||
|
||
Year to year comparison, by commit: | ||
|
||
- Q2 2022 - 474 commits. 59% from IBM. | ||
- Q2 2023 - 272 commits. 64% from IBM. | ||
|
||
Year to year comparison, by contributor: | ||
|
||
- Q2 2022 - 68 contributors. 28% from IBM. | ||
- Q2 2023 - 46 contributors. 24% from IBM. | ||
|
||
# Additional Information | ||
|
||
[Insights dashboard link](https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Ffabric/dashboard;subTab=technical?time=%7B%22from%22:%222023-04-01T04:00:00.000Z%22,%22type%22:%22absolute%22,%22to%22:%222023-07-01T05:00:00.000Z%22%7D) |