Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 10 Current »

Summary:

Topics:

  • Upgrade the ACA-Py Python version – to what?
  • BC Gov Activities planned
  • Q&A

Recordings from the call: 


Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Attendees

Announcements

Deployments and Work Updates

Agenda

  • Upgrading the version of Python used by ACA-Py
    • 3.6 is end of life'd, so this is a high priority
    • 3.7 PR, but 3.7 is less than a year from end of life
    • Other versions lifespans
    • Why not use 3.10?
    • Discussion:
      • On 3.7 branch, all tests are passing, but with lots of deprecation warnings
      • 3.6 to 3.7 is likely the biggest breaking change (vs. going to 3.8, 3.9, etc.)
      • 3.11 evidently has a significant performance improvement (e.g. 25%), so being ready is important
      • Suggested approach:
        • 3.7 branch for now
        • Add GHAs to run all tests on all Python versions 3.7 - 3.10.
          • Run one version on PRs (same as today)
          • Run other versions daily on a cron
        • Add tag-based publishing of artifacts, and publish to the Hyperledger GitHub Container Repository
      • Adam Burdettand team to produce a HackMD doc about the plans to promote comment and community collaboration
      • Vulnerabilities associated with OS being used for the current BC Gov Images was raised – to be reviewed and possibly updated
        • But we really want to go to tag-based publishing per note above.
  • An overview of BC Gov's priorities/focus – presentation
    • Revocation updates – so close...
    • Completing/documenting/testing persistent queues and shared cache
      • Possible alternative solution to the shared cache – look at the current connection handling, where caching is being used and persist the data
    • Additional Aries Askar support for migration and shared component updates
      • Request about whether contributions to improve performance in high volume use cases (e.g. 400k wallets) would be generally useful
        • Assuming the low volume cases would not be massively impacted – yes, that would be helpful
    • AIP 2.0 updates, especially focused on DID Exchange – did:peer and did:key – with a goal of alignment with Aries Framework JavaScript (as demonstrated by AATH).
    • OCA support as needed.
    • Aries Endorser Service.

Next Meeting

Future Topics

Action items


  • No labels