2021-01-05 Indy Contributors Call

Summary

Recording from the call: 2020-12-22 Indy Contributors Call Recording

Welcome and Introductions

Attendees

• @name (Employer) <email>

Related Calls and Announcements

• TBD

Release Status and Work Updates

• Indy Node
  • Next release in progress, led by this team using a revised CI/CD process
• Indy SDK
  • Next release in progress, led by Ian Costanzo
• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
• Indy/Aries Shared Libraries
• Ursa

Meeting Topics

• Request from Marta Piekarska-Geater: We should mark "good 1st bug" at time of submission for use by Hyperledger in developer activities
• Indy Node Release
  • Process:
    • Fix Jenkins so that we have a build to compare with (Evernym)
    • Setup Github Actions / Azure CI pipeline (Kevin)
    • Show that a release through Github is the same as through Jenkins
    • Migrate to Ubuntu 20.04 (Evernym)
    • Start releasing from Master instead of Stable (Wade)
  • Goals (ranked):
    1. CI / CD on GitHub Actions

    2. Switch from Indy Crypto to Ursa

    3. Update from Ubuntu 16.04 to Ubuntu 18.04 / Ubuntu 20.04

       1. When updating validator nodes, note that there is a bug that prevents catch up from an empty ledger. Must copy data to the new machine then catch-up.
       2. During the upgrade, it's better to have different versions of Ubuntu with same version of Indy Node then run for an extended period of time with different versions of Indy Node.
    4. New branching model to release from Master with tags
       1. Promote Stable to Master, then deprecate Stable
    5. Release work in Master

       1. Using a feature flag to prevent usage of new Rich Schemas transactions.

    6. Potential features to assist with removing token from Sovrin networks

       1. Stub unused ledgers from removed plugins
       2. Fees as a Node concept
  • Potential releases:
    • CI / CD Change, released from Stable
      • indy-crypto: use existing artifact
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: generate from Jenkins
      • sovrin-node: generete from Jenkins
      • ursa-crypto: exclude
    • Remove Token, released from Stable
      • indy-crypto: use existing artifact
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: stub or exclude
      • sovrin-node: generete from Jenkins
      • ursa-crypto: exclude
    • Upgraded Ubuntu, release from Stable
      • indy-crypto: exclude
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: stub or exclude
        • If necessary, could try to release with existing token-plugin
      • sovrin-node: generate from Jenkins
      • ursa-crypto: existing artifact
    • Release without Stable (move what is Master today into a branch)
      • indy-crypto: exclude
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: stub or exclude
        • If necessary, could try to release with existing token-plugin
      • sovrin-node: generate from Jenkins
      • ursa-crypto: existing artifact
    • Release New Features (merge former Master branch back to Master)
      • indy-crypto: exclude
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: stub or exclude
        • If necessary, could try to release with existing token-plugin
      • sovrin-node: maybe new Github CI / CD
      • ursa-crypto: existing artifacts

Future Calls

Next call:

Future:

Action items