Page History

...

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

...

• Proposal: BC Gov to contribute the indy-shared-rs repo to Hyperledger
  • A companion repo to indy-vdr (already contributed to Hyperledger) and aries-askar (also proposed for contribution)
• Indy Node Release
  • Process:
    • Fix Jenkins so that we have a build to compare with (Evernym)
    • Setup Github Actions / Azure CI pipeline (Kevin, Wade)
    • Show that a release through Github is the same as through Jenkins
    • Start releasing from Master instead of Stable (Wade)
  • Goals (ranked):
    1. Release using CI / CD on GitHub Actions

    2. 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.
    3. New branching model to release from Master with tags
       1. Promote Stable to Master, then deprecate Stable
    4. Release work in Master

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

    5. Switch from Indy Crypto to Ursa

    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: generate from Jenkins
      • ursa-crypto: exclude
    • Upgraded Ubuntu, release from Stable
      • indy-crypto: use existing artifact / release from Jenkins / exclude from release (if necessary)
      • indy-plenum: generate from new GitHub CI / CD
      • indy-node: generate from new GitHub CI / CD
      • token-plugin: generate from Jenkins/use existing artifact
      • sovrin-node: generate from Jenkins
      • ursa-crypto: excluse from release / use existing artifact (if necessary)
    • Release without Stable (move what is Master today into a branch)
      • Same components/sources  as previous release
    • Remove Token, released from Stable (There is not agreement this is desirable now vs. other priorities)
      • 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
    • 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
• Indy SDK Release - Ian Costanzo
  • RC ready and being tested – w00t!!
• GitHub Actions for the Indy SDK – ABSA contribution

Future Calls

Next call:

Future:

...