You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »


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:

  1. V2.0 release status: Pam/Joe–
  2. Documentation style technology (Besu comparison)
  3. New process for submitting changes without gerritt Unable to render Jira issues macro, execution error.
  4. Upgrade docs (Joe) — will show staged docs used with above process
  5. New test network (BYFN replacement) latest updates: Nik
  6. MSP follow-up https://github.com/hyperledger/fabric/pull/297

Discussion

  1. Release status from Pam and Joe
    1. Steady progress on V2
    2. Working on V2 beta - still targetted December
    3. Upgrade docs (see later)
    4. Official cut from Gerrit to GitHub
    5. BYFN replacement progress from Nik with V2.0 Beta
    6. Chaincode launcher next Wednestday
    7. Ledger API discussion
  2. Stay tuned for progress on Besu.
  3. Gerrit/GitHub discussion from Pam
    1. Doc team experimenting in last few days
    2. All references to Gerrit removed in Master & 1.4
      1. GitHub now standard
    3. Contributions updated: https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html
    4. Some guidance notes in JIRA:  Unable to render Jira issues macro, execution error. on comparative usage
    5. Short guided tour by Pam - thank you.
    6. Pam also showed Azure Pipeline and download to local machine for viewing
    7. Can still run local builds as usual, and showed use of /azp run command for triggered builds
    8. Overall working well and positive experience
    9. Moved new MSP topic to GitHub!
    10. Some questions on how suggested reviewers and comments work. Add Chris and Jim
  4. Upgrade docs from Joe
    1. Reviewed old structure: observation on comprehensibility
    2. Walked through new upgrade doc
    3. New approach is for release specific upgrade topic to reference specific upgrade task via links. These linked-to tasks are kept separate.
      1. This separation of concerns helps usability and maintenance of upgrade/migration doc
    4. Provides better relationship to tutorials
    5. See video for example on Peer database upgrade.
    6. Positive feedback on this structure.
  5. Brief updated from Nik on BYFN
    1. Re-base on Fabric 2.0
    2. New tutorial-oriented BYFN will be added
    3. Probable Removal of CLI container, to make more production-like
    4. Will not upgrade BFYN as part of docs
    5. Parallel running of old and new - co-existing during migration
    6. More BYFN detail in next meeting
  6. MSP follow-up deferred to next meeting


Video of this week's session at: Recordings

Quarterly reports

Upcoming reports

Backlog



  • No labels