Release 1.3.0 #148
Merged
Release 1.3.0 #148
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release 1.2.0
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]>
Bump UCO to current state of develop
No effects were observed on Make-managed files. References: * ucoProject/UCO#536 Signed-off-by: Alex Nelson <[email protected]>
UCO Issue 536: Bump UCO to current state of develop
No effects were observed on Make-managed files. References: * ucoProject/UCO#541 Signed-off-by: Alex Nelson <[email protected]>
UCO Issue 541: Bump UCO to current state of develop
No effects were observed on Make-managed files. References: * ucoProject/UCO#563 Signed-off-by: Alex Nelson <[email protected]>
UCO Issue 563: Bump UCO to current state of develop
No effects were observed on Make-managed files. References: * ucoProject/UCO#571 Signed-off-by: Alex Nelson <[email protected]>
UCO Issue 571: Bump UCO to current state of develop #141
No effects were observed on Make-managed files. References: * ucoProject/UCO#579 Signed-off-by: Alex Nelson <[email protected]>
This ports the patch from UCO PR 579. References: * ucoProject/UCO#579 Signed-off-by: Alex Nelson <[email protected]>
Update change request template
A follow-on patch will regenerate Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
A follow-on patch will regenerate Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
|
This PR is ready for review and merge. |
plbt5
approved these changes
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Coordination