Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add submodule status to supply chain review #54

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

ajnelson-nist
Copy link
Member

No description provided.

@ajnelson-nist ajnelson-nist self-assigned this Apr 5, 2023
@ajnelson-nist ajnelson-nist merged commit 59910c9 into main Apr 5, 2023
@ajnelson-nist ajnelson-nist deleted the add_submodule_status_review branch April 5, 2023 18:04
ajnelson-nist added a commit to casework/CASE that referenced this pull request Apr 5, 2023
This patch is solely about Git submodule logistics, and carries no
semantic impact on CASE.

This patch is necessary for some "downstream" submodule synchronization.
The CASE `develop-2.0.0`, `unstable`, and `unstable-2.0.0` branches
should share a history point where the UCO submodule state is at its
post-release `develop` status.  Otherwise, catch-up merges of CASE's
`develop` into other CASE branches will encounter Git merge conflicts
pertaining to the submodule.

This is a consequence of the plan laid out in UCO Issue 493, which was
somewhat expected.  However, recent trial practices in guaranteeing
submodules are up to date (e.g. `case-prov` PR 63 and CASE-Corpora PR
54) have brought the issue to light, given the CASE `unstable` branch is
currently behind the release rather than ahead of it, and needs
`develop` updated to avoid the submodule-based merge conflicts.

References:
* casework/CASE-Corpora#54
* casework/CASE-Implementation-PROV-O#63
* ucoProject/UCO#493

Signed-off-by: Alex Nelson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant