Closed ajnelson-nist closed 3 months ago
This PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This PR is part of delivering UCO Issues 562, 586, and 590 via the CASE website.
This PR also catches CASE's develop-2.0.0 up with develop, including handling Git submodule logistics.
develop-2.0.0
develop
This PR is ready for review and merge.
@plbt5 Our 2-key protocol is the submitter doesn't typically merge. This leaves 2-key easier to see in the Git history offline from GitHub.
This PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This PR is part of delivering UCO Issues 562, 586, and 590 via the CASE website.
This PR also catches CASE's
develop-2.0.0
up withdevelop
, including handling Git submodule logistics.