Versions Compared

Old Version 3

changes.mady.by.user Kevin Griffin

Saved on

compared with

New Version Current

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 Ubuntu 20.04 18.04 work
  • Status of upcoming indy-node release, Rich Schema Feature Flag, and CI/CD Progress
  • Status of upcoming indy-sdk release

Recording from the call: 20201208 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

...

  • Meeting schedule over Christmas and New Years? (Dec 22 and Jan 5)
    • Will continue with the meetings, but with reduced attendance.
  • Ubuntu 20.04 18.04 for Indy Node / Indy Plenum
    • PRs for Plenum and Node for 18.04 ready to be merged and tested
    • Confirmation on this approach? Yes - no objection
        Copy
        • If we continue with Jenkins for CI/CD, we need to copy and run two versions of the pipeline one for 16.04 and 18.04
        • However, no one knows how to do this is – we're stuck.
      • Decision: Time to ditch Jenkins and move to GitHub Actions once and for all. It would be nice to run both, but the risk of not being able to move forward at all is a bigger concern.
        • New team led by Wade, Kevin and Steve McCowan will work on getting this done, with questions to the Evernym team.
        • Not discussed, but ideally, in the process of this we:
          • Get rid of the split plenum/node pipelines, and
          • We eliminate the use of Master, Stable and RC branches, going to just Master (Main) and PR branches in the common case; feature and fix branches if and when needed.
      • Indy Plenum PR Review - the consensus code - Any updates to status?
      • Replace indy-crypto with ursa-crypto – build failing, Wade Barnes investigating.
        • PR to fix, but there is a dependency to indy-plenum in order to proceed.
        • Still stuck on indy-plenum
      • Rich Schema feature flag merged
      • CI/CD Progress
        • Brent's fix for INDY-827 (PR 1486)  - not to be merged into main until reviewed and tested by another
          • Decision: Will not be merged into this release because of the manual testing effort.
        • Need to accept PR 1482 - Evernym can do that.
        • What is the difference between STABLE and MASTER
          • Stephen to review the last call recording - couldn't find anything
          .
      • Arrange a meeting to get the CI/CD done, or perhaps merge the code bases to enable a single pipeline.
        • Plenum PR created
        • One test is failing – likely not because of the CI/CD – failed previously
        • Plan is to get this done entirely
      Indy Node Release Status Updates:
          • on the recording – still not understood.
    • Request for indy-sdk release
      • RC branch ready to go, release notes updated, everything is almost ready to goProblem: IOS branch is not building.  What do we do?
      • Sergey has a PR that seemed to work, and build is in progress for that.
      • If so – Master to RC and we're good to go.
      • Could drop IOS, but we'd really rather not do that.
        • Point people: Sergey, Ian, Steve McCowan, Wade
      • IOS 64-bit only, 32 bit being dropped
      • Jenkins pipeline for Windows is not working – locked out of the infrastructure
        • Wade working on cloning the VM and wire it back up - risk is that the VM has been manually updated over time, but not clear
        • The VM is a Jenkins master controlling the ledgers for testing.
      • One commit in Master Branch is not DCO signed .
        • Someone manually bypassed the DCO which allowed us to proceed – a very bad practice.
          • Separate issued – Ry to be asked if that button can be turned off. 
        • Fixed in the RC branch – not touched in the Master Branch
        • How to address in the Master Branch?
        • Ian, Wade and Ry to discuss.
      • Should we release now or get more features in?
        • No one requested more be added
      • Should this be the last indy-sdk release?Evernym would like to free up the team to do other things, so would like to know if more effort is to be put into the indy-sdk?- RESOLVED - force push into Master
      • Mac issue – 32 bit support is being dropped, 64 bit will continue to be supported
      • Rust issue – need to consider when to switch to newer version.
    • Richard to put in a PR to say that indy-sdk is deprecated – discussion to follow.

    Future Calls

    Next call:

    Future:

    ...