Guest post: Hyperledger Fabric 1.1 release manager, Chris Ferris
One of the questions I am often asked is “Is there a roadmap for Hyperledger Fabric development?” I usually to point people to the Hyperledger Fabric wiki, because for the most part, we try to be pretty transparent about plans for our next release. Our challenge is to try to make the information a bit more visible and accessible.
Since we launched Hyperledger Fabric 1.0.0, the maintainers have published patch releases on a (roughly) monthly basis (v1.0.1 – v1.0.4). We want to continue to deliver monthly patch releases on the 1.0.0 release branch until we release Fabric 1.1.0 sometime in Q1 2018, at which point we will discontinue patch releases for the 1.0.x release branch and start publishing monthly patch releases for 1.1.x release branch.
Our roadmap plan (generally) is to publish approximately one minor release per quarter once we get v1.1.0 finished. We will be also be exploring the adoption of a long-term support (LTS) strategy possibly starting with the v1.2.0 release. What this would mean is that the maintainers would continue to publish patch releases on a designated LTS release for up to a year (initially) afterwards, even if we publish a major or minor release in the interim.
As for which new features we’re tracking in the roadmap for the 1.1.0 release, those can be found in the wiki, as well. The wiki also links to each feature’s JIRA item which tracks the feature development and would typically include any design documents, etc.
We are also tracking a set of experimental features that can be enabled through a re-compile of the Hyperledger Fabric codebase via the wiki. You can generally expect, that these experimental features would be formally supported in the subsequent release (1.2.0 in this case).
We also track the progress of each feature in our next release in our JIRA dashboard (see gadget in the upper left).
The Hyperledger Fabric Maintainers are always interested in feedback (positive and negative) as well as proposals for new features. Anyone can weigh in through one or more of the various communication channels (chat, email, or posting directly to JIRA) and either offer recommendations, or specific proposals.