Continuing to keep in step with the latest Hyperledger Fabric v1.0 changes

Delivered connection profile and identity management support in the playground:

Use connection profiles to connect to Hyperledger Fabric v0.6 and v1.0.

Use identity management to switch between different Blockchain identities.

Removed and deprecated the old, superseded UI

Upgraded the Angular generator to generate Angular 4 applications.

Began work on being able to model, publish, and subscribe to business events.

Hyperledger Fabric

We agreed to a feature/code freeze at the Hackfest in DC, and selected co-release managers for the v1.0 release: Chris Ferris (IBM) and Jonathan Levi (Hacera).

At the hackfest, we also discussed and agreed on some changes to the development process proposed by Dave Huseby, which we will implement as a function of creating the release branch for v1.0.0-alpha2.

The TL;DR: of the proposal is that we will manage change through feature branches that will be merged into a development branch to undergo the full gauntlet of testing, and reverted if they still need work. Once the development branch has merged the set of features agreed for a release, the develop branch will be fast forward merged into the release branch (also the master branch), tested once more, and then published. The release/master branch which will always have the most recent stable release as the default on GitHub (as opposed to the head of development as is the case today).

Hyperledger Fabric added three new maintainers to help keep reviews up with the pace of change requests.

The rate of bug fixing has consistently outpaced reporting for the past 3 weeks, with in excess of 50 defects resolved per week.

The unit test coverage has seen steady improvement, now more than 70% (it had been 61%) with many key areas of the code at 100%. The integration test framework is taking shape and we expect to have regular testing (daily, performance/scale and long running) operational shortly.

Maintainers cut a v1.0.0-alpha2 release the week of May 8

Hyperledger Indy

Hyperledger Indy team is currently planning Jira migration from Sovrin to Hyperledger and working on configuration post-Jira Upgrade

Planning migration of code from Sovrin GitHub to Hyperledger GitHub

The team is identifying participants for Healthcare, Performance and Scaling WGs as well as collaborators for Hyperledger Burrow and Hyperledger Composer