As one of the Hyperledger Fabric Maintainers, one of the questions I am often asked is “What is the roadmap for Hyperledger Fabric development?”. My response is to point people to the Hyperledger Fabric wiki, because for the most part, we are pretty transparent about plans for our next release. Beyond that, things are a little fuzzy. As a community, we have not gotten to the point yet that we are planning multiple releases in advance.
The Hyperledger Fabric community published our 1.0.0 release of Fabric this past July. Since then, we have published patch releases on a (roughly) monthly basis (v1.0.1 – v1.0.4). The Hyperledger Fabric Maintainers’ intention is to continue to deliver monthly patch releases on the 1.0.0 release until we release 1.1.0 sometime in 1Q2018, 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 of releases is to publish approximately one minor release per quarter once we get v1.1.0 published. We will be also be exploring the adoption of a long-term support (LTS) strategy starting with v1.2.0. What this would mean is that the Maintainers would continue to publish patch releases on a selected LTS release for up to a year (initially) afterwards, even if we publish a major or minor release in the interim.
As for specifically what new features we’re tracking in the roadmap for the 1.1.0 release, those can be found in the wiki, as well. There’s not much to add, because the wiki also links to each feature’s JIRA item which tracks the feature development and would typically include any design documents, etc.
Note that we are also tracking a set of experimental features that can be enabled through a re-compile of the Fabric codebase. You can generally expect, that these 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 and proposals for new features. Again, because this is open source, anyone can weigh in through one or more of the various communication channels (chat, email, or posting directly to JIRA).