Strategy for deprecating old MSP messages?

[sensei-hacker]

Pawel had suggested removing some MSP V1 messages which have MSPv2 replacements from INAV.

https://github.com/iNavFlight/inav/pulls?q=is%3Apr+is%3Aopen+msp

From the MWP point of view, what might be the best way to handle this? Would it be best if INAV not remove messages at all? Should there be a deprecation process? What are your thoughts?

[stronnag]

mwp doesn't care. If the FC supports MSPv2, it uses MSPv2; otherwise it uses MSPv1 and legacy messages.
The issue is that other, 3rd party legacy tools what don't offer this version related sophistication will break.

As a general principle. INAV should announce deprecation in version N, deprecate the function in v N+1, remove in v N+2.
Exemplar of this approach: iNavFlight/inav#9868 and iNavFlight/inav#10362

Note: This is not a mwptools discussion, it is an INAV discussion.

[sensei-hacker]

Thanks! Sounds like it would not cause a problem for MWP.

I'll reach out separately to maintainers of an other known affected software just to give them a heads up of deprecation or whatever.