[WIP] Move MAV_CMD_DO_UPGRADE to development.xml #1720
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
31 tasks
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.
MAV_CMD_DO_UPGRADEwas added in #1382 as WIP but appears to have no implementation in PX4.We are trying to clean up common.xml of WIP features, and more generally of those that do not comply with the governance model. Work for this is being tracked in #1669
NOTE I have confirmed from @TSC21 that this is not yet in PX4, and may not even be in use by customers upstream of PX4. I am therefore merging this to move it into development.
I am also going to create another PR to remove it from development.xml - I don't want to break upstream but this message is not great.