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
...
- V2.0 release status: Pam/Joe
- Documentation style technology
- New process for submitting changes without gerritt
Jira Legacy server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-17122 - Upgrade docs (Joe) — will show staged docs used with above process
- New test network (BYFN replacement) latest updates: Nik
- MSP follow-up https://github.com/hyperledger/fabric/pull/297
Discussion
...
- Release status
- Steady progress on V2
- Working on V2 beta - still targetted December
- Upgrade docs (see later)
- Official cut from Gerrit to GitHub
- BYFN replacement progress from Nik with V2.0 Beta
- Chaincode launcher next Wednestday
- Ledger API discussion
- No forward progress on Besu - stay tuned!
- Gerrit/GitHub discussion
- Doc team experimenting in last few days
- All references to Gerrit removed in Master & 1.4
- GitHub now standard
- Contributions updated: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html
- Some guidance notes in JIRA:
on comparative usageJira Legacy server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key FAB-17122 - Short guided tour by Pam - thank you.
- Pam also showed Azure Pipeline and download to local machine for viewing
- Can still run local builds as usual, and showed use of /azp run command for triggered builds
- Overall working well and positive experience
- Moved new MSP topic to GitHub!
- Some questions on how suggested reviewers and comments work. Add Chris and Jim
- Upgrade docs from Joe
- Reviewed old structure: observation on comprehensibility
- Walked through new upgrade doc
- New approach is for release specific upgrade topic to reference specific upgrade task via links. These linked-to tasks are kept sepearate.
- This separation of concerns helps usability and maintenance of upgrade/migration doc
Video of this week's session at: Recordings
...