...
- #3663 Fabric v3 epic misc items
- #3306 new channel config MaxWriteSize, prevents large writes that potentially exceeds CouchDB max_document_size
- #3343 ed25519 support
- #3650 fabric-protos Go bindings based on protocol buffer APIv2 (v1 protobuf is deprecated) - potential deferral
- #3704 older v3 ideas from Jira - e.g. Remove support for remaining Go plugins (endorsement and validation plugins) - potential deferral
June 19, 2024 (recording)
- Recent Fabric releases
- Fabric v2.5.9, CA v1.5.12 - June 18
- Dependency updates
...
- Need to finish
- Finish SmartBFT
- Finish tests
- Fix frequent test failures in SmartBFT unit tests and integration test
- Finish v1 chaincode lifecycle removal - keep external APIs but just return an error message - Tatsuya can help Artem
Legacy lifecycle has been removed from integration test and peer cli, meaning no one could use it.
Updated tests and removed logic that relied on legacy LCC.
What is still to be done?
Need to remove the initialization of the LSCC code as a chaincode (in progress)
Need to ensure peers won't crash in case we get connected to the legacy system, meaning the system is probably being upgraded. We need to ensure newly joined peers won't crash on instantiate transactions; the validation part should still be aware of these updates.
The last thing is mostly cosmetics to refactor the code to move or fuse legacy validation logic with new _lifecycle.
- Ensure all documentation is updated
- Change peer property blockGossipEnabled default to false - Block dissemination via gossip already deprecated in v2 (recommendation is to configure all peers as org leaders to receive blocks from ordering service) - https://github.com/hyperledger/fabric/pull/4911
- Finish SmartBFT
- #3663 Fabric v3 epic misc items
July 17, 2024 (recording)
- Release update
- Remaining v3 release work item - finish v1 chaincode lifecycle removal (see June update above for details)
- Creating a project charter for Fabric - Sean Bohan (Linux Foundation)
- Draft project charter text
- The goal of having project charters is to follow open source best practices and to make the governance of Hyperledger projects more clear, transparent, and easily discoverable
- Please review by July 31 and make any edits if needed on the doc in suggestion mode so we can see what changes you are proposing
- If you have any questions about this, let us know and we can help
- v2 Go chaincode API (using v2 protocol buffers) - Mark Lewis
View file | ||||
---|---|---|---|---|
|
August 21, 2024
- v3 release preparation
- remove v1 capabilities? See https://github.com/hyperledger/fabric/pull/4954
- blog post
- documentation
- Fabric project charter