Page Comparison

Summary

Recording from the call: <To Be Added>

Welcome and Introductions

...

• Update on CI/CD Update and Ubuntu Upgrade: Status Document
  • General
    • Wade will be working at documenting the required work in GitHub issues.
  •  Indy-Plenum
    • 16.04 PR has been merged.  Artifact were published to https://hyperledger.jfrog.io/ui/repos/tree/General/indy%2Fpool%2Fdev%2Fi%2Findy-plenum%2Findy-plenum_1.13.0~dev106_amd64.deb
    • Python packaging is being added to the 16.04 branch
    • 20.04 PR is a work in progress (Robin/Wade working on this)
      • Issues with hanging tests were identified; https://github.com/hyperledger/indy-plenum/issues/1546
        • The workaround required pinning RocksDB to 5.8.8.
        • A ticket will be created for the RocksDB upgrade (Focal uses 5.17)
          • Can upgrade RocksDB in the next release after we drop support for Ubuntu 16.04 (all validators have upgraded)
        • List of other dependencies that require code changes to unpin
          • Should investigate for the next release.
    • Wade have been experimenting with the Remote-Containers extension for VS Code and created a dev container for indy-plenum development on Ubuntu 20.04; https://github.com/WadeBarnes/indy-plenum/tree/ubuntu-20.04-dev-container
      • This was initially created in the later stages of the RocksDB issue investigation.  So it still contains RocksDB 5.17.
    • Hyperledger Indy-Plenum | Dependency management
  • Indy-Node
    • Work on Node was delayed due to the investigation of the hanging tests and the collaboration on the Python packaging.
    • Work on Node should commence again this week.
  • Sovrin Release - Wade Barnes
    • Work will resume following the work on Plenum and Node.
    • Once it's complete, Evernym can test the release candidate.
  • indy-test-automation
    • Work will continue as/when needed.
• Indy Plenum issuer reported: IC Queue getting quite large
  • Dom to add more details; Evernym to look furtherEvernym has provided feedback and Dom is looking into things further on his end.
• Indy SDK
  • Indy CLI is part of the Indy SDK
  • Async libindy https://github.com/hyperledger/indy-sdk/pull/2319 - what's the plan?
  • IndySDK LibVCX - should be removed from IndySDK?
  • Should Indy CLI be part of indy-node or put into it's own repository.
    • Could it pulled out and put on indy-vdr?
    • Possibly post as a help wanted – pulling out of indy-sdk and into indy-cli

...