Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct
Announcements
This week's agenda is:
- V2.0 release status: Pam/Joe
v1.4.4 targeted for November
- bug fixes
- Also shifts fabric docker images from ubuntu to debian:buster-20190910-slim - smaller images, more secure
- note - v2.0 shifts to alpine images - even smaller, even more secure
v2.0.0-beta targeted for December, remaining items that we are trying to close down:
- external chaincode documentation
- external chaincode as a server
- state database cache for improved performance
- upgrade documentation
- node sdk v2.0 refactoring - in master split fabric-client into fabric-base (for transactions) and fabric-admin (for v2.0 lifecycle support)
- please go through Jira backlogs and help to highlight anything that needs to get in before v2.0
- Chris Gabriel demo
The fabric-samples repository has moved over to use the combination of Github for code, and Azure pipelines for CI:
fabric-sdk-java Move complete FABJ-486
fabric-gateway-java Move complete FGJ-48
fabric-sdk-node In progress FABN-1386
fabric-chaincode-java Move complete FAB-16712
fabric-chaincode-node Move complete FAB-16711
- Status of proposal to convert the docs to the Besu readthedocs template. http://besu.hyperledger.org/en/latest/
- BYFN update feedback
- MSP key concepts update proposal
Discussion
- Discussed current release status.
- Highlights as above
- Upgrade docs discussed. Separate docs for each concern: configuration, channels on per release basis (starting with V2.0)
- Chris shared perspective that this is important for self-managed systems, i.e. base Fabric rather than a managed service
- Chris also mentioned difference between containerized production systems and local development systems e.g. Cryptogen vs Fabric CA, wallets and containers...