Steps to v3

[julianoes]

Things I have planned for v3:

API breaks

• Improve list_directory API #2308
• Change RTK to base64 #2314
• Switch to clearer API for UDP and TCP #2315

Adopt new messages

• Camera plugin uses deprecated messages #1605
• REQUEST_MESSAGE vs custom getters like REQUEST_CAMERA_INFORMATION #2013
• Remove gimbal v1 #2317
• Remove old calibration params #2318
• Support opaque mission ID #2324

Remove hacks

• Why MAVSDK doesnt create a new system for telemetry radios? #2302

Nice to have

• CI: add macOS arm runners and update macOS CI in general  #2277
• Gimbal API redesign (support more than one gimbal, support streams and commands) #2363
• Camera: support more than one camera with one plugin instantiation #2365

[Pjort]

Is there any chance that v3 can ship without all the "Nice to have"?

Since to me it looks like the only thing holding back the v3 release is "multi camera support" which is in the "Nice to have" category. And this has been the case for 4-5 months now I believe.

[julianoes]

I have done the bulk of the refactoring work, and it's ultimately what I need v3 for, so I guess it's more than nice to have for me.

It's now just pending system_tests failing on macOS. Since I don't have a Mac, I rented a Mac in the cloud to try to reproduce the issue. And guess what, the tests work just fine there, so it's something odd with GitHub actions mac runners, very frustrating...

[Pjort]

I have done the bulk of the refactoring work, and it's ultimately what I need v3 for, so I guess it's more than nice to have for me.

It's now just pending system_tests failing on macOS. Since I don't have a Mac, I rented a Mac in the cloud to try to reproduce the issue. And guess what, the tests work just fine there, so it's something odd with GitHub actions mac runners, very frustrating...

I see. I have an MacBook available to me, and I can help test stuff if needed. But if it is a GitHub actions problem I am not sure how I can help.

[julianoes]

Thanks @Pjort. It presumably only happens on macOS CI because it's somehow running slow or in bursts. In any case @JonasVautherin stepped in to help and was able to somewhat reproduce and fix it!