Versions Compared

Old Version 1

changes.mady.by.user Richard Esplin

Saved on

compared with

New Version 2

changes.mady.by.user Stephen Curran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

Excerpt

Planned:

  • Status of indy-node CI/CD progress
  • Status of upcoming indy-sdk release

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

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

  • @name (Employer) <email>
  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

Related Calls and Announcements

...

  • Indy Node
    • Next release in progress, led by this team , same content as the last release, but using a revised CI/CD process for at least indy-plenum and indy-node
  • Indy SDK
  • 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, Wade)
      • Show that a release through Github is the same as through JenkinsMigrate to Ubuntu 20.04 (Evernym)
      • Start releasing from Master instead of Stable (Wade)
    • Goals (ranked):
      1. Release using 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. Switch from Indy Crypto to Ursa

      7. 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 generate from Jenkins
        • ursa-crypto: exclude
        Remove Token
      • Upgraded Ubuntu, released release 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/ 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: stub or excludeIf necessary, could try to release with existing token-plugingenerate 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: excludeuse existing artifact
        • 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 generete from Jenkins
        • ursa-crypto: existing artifactexclude
      • 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

...