Added Submodule Compatibility Guide #64
Merged
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
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.
PR Details
Description
The documentation now provides a useful table to guide users in selecting compatible versions of submodules for their chosen version of the project.
Related Issue
No related issue.
Motivation and Context
Previously, users lacked guidance on which submodule versions were suitable for a specific version of the project. They had to resort to methods like checking release dates, inspecting git submodule commits, or relying on the 'latest' tag on DockerHub, which was often uncertain. This update aims to simplify the deployment process.
How Has This Been Tested?
Since this update involves documentation only, no testing is required.
Types of changes
Checklist:
ODE Contributing Guide