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

Compare with Current View Page History

« Previous Version 7 Next »

Summary:

Topics:

  • Release 0.10.1 Published
  • AATH Issue – ACA-Py Tests Failing since 2023.09.01
  • DID Peer discussion – Across Aries and ACA-Py-specific
  • PRs and Issues - status update
  • Open Discussion

Zoom Link: https://zoom.us/j/98856745538?pwd=VkJROWRxeW43d3hOdnJLemwrS0JKUT09

Call Time: 8:00 Pacific / 17:00 Central Europe

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, Introductions and Announcements

Attendees


Announcements

Agenda

  • Release 0.10.1 Published
  • AATH Test Failing – last passed 2023.08.29, first failed 2023.09.01
  • DID Peer Progress and Discussion
  • Update: Hyperledger AnonCreds Rust in ACA-Py
    • Status of AnonCreds RS – has merged in the latest CL Signatures.
      • No release has been done. Need to get that done ASAP - Andrew or Timo?
      • Following that, Daniel will get main merged into the AnonCreds RS branch in ACA-Py.
  • PRs and Issues
    • Old ones (suggested for discussion by Daniel Bluhm): 
    • What would LTS (Long Term Support) support mean for ACA-Py?
      • Commitment from an organization to provide the support
        • Keep the infrastructure to keep running – e.g. GHA for now – but monitor changes in that.
      • Time frame for the LTS – 3 years, 5 years?
        • Plan for the "next LTS"
      • Get to a 1.0 version?  E.g. AIP 2.0?  Getting close... 
        • Please ACK – needs to be implemented.
      • Pick an LTS OS to run on
        • Target the version of Python associated with the OS and other dependencies
          • All python releases get 5 years of security updates (starting from release date)
          • Python 3.9 ends October 5, 2025
      • Monitor OS and dependencies and update them on a branch
      • Cherry pick ACA-Py PRs suitable for LTS
        • CI/CD Infrastructure changes – maintain them for the LTS 
        • Security fixes - Yes
        • New features – No
      • Marketing/Guidance – the positioning of LTS versions and the ongoing evolution of the codebase
      • Interoperability – maintenance of the test harness – e.g. adding a Test Agent for the LTS branch ongoing execution
        • AATH – need feature to NOT run tests when the Test Agent has not changed
      • Migration – migration to the next LTS – managing that, perhaps beyond what we do in ACA-Py today
      • Impacts on Community Coordinate Updates
        • Should we, for example, support step 1 of CCUs by adding handling receipt of old and new?
  • Open Discussion

Upcoming Meeting Topics:

  • Discussion Topics:
    • Update on ACA-Py Container Scanning
    • Multi-architecture containers
      • Issue with BBS+ package – doesn't support ARM containers – need an update to their CI
      • Solution: A third container published that includes BBS+ package, but is single architecture
      • Others are Askar

Future Topics

Action items


  • No labels