update README and kraken_nav/README #272
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
Signed-off-by: Jan Hanca <[email protected]>
|
Switching to draft, |
Signed-off-by: Jan Hanca <[email protected]>
Signed-off-by: Jan Hanca <[email protected]>
|
Based on the internal discussion with @adamdbrw it was decided to completely remove the outdated |
arturkamieniecki
approved these changes
Dec 19, 2023
Signed-off-by: Jan Hanca <[email protected]> Co-authored-by: Artur Kamieniecki <[email protected]> Signed-off-by: Jan Hanca <[email protected]>
jhanca-robotecai
force-pushed
the
jhanca-robotecai/update_readme
branch
from
e2373bb to
a8f7ced
Compare
This was referenced Dec 19, 2023
Closed
michalpelka
approved these changes
Dec 20, 2023
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.
There are some inconsistencies and duplications between the main
README.mdandkraken_nav/README.mdfiles. The major problem was indicated recently in #270 and #271: one of the readme files was suggesting usage ofmainbranches, while the other one was pointing todevelopmentbranches ofo3deando3de-extras. This is fixed now. Additionally, a comment about2310.1release was added - this should be a default version for all users.Creating this PR to be merged into
development. Following this change, thedevelopmentbranch should be merged into themainbranch, as this codebase was thoroughly tested with2310.1and works correctly. The current HEAD ofmainbranch was last updated on Dec 1, 2022 - it is time to update it.