Closed ajnelson-nist closed 1 year ago
For our awareness:
The similar PR to catch develop-2.0.0
up with develop
had to be done outside of GitHub. That merge commit is here. It's likely a similar offline catch-up merge will have to be done once after each CASE release.
This PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This is a semi-mechanical PR similar to UCO PR 533. The patch includes an explanation for the timing, as this has typically come later in past releases' development cycles.