Getting ready for next release

I have implemented all the features I plan to for the next release.
I have introduced a lot of new code recently and much of it is very lightly tested. So the next few weeks will be spent cleaning up any interface issues, fixing bugs, and generally polishing for release.

I wouldn't recommend translators to start yet. The new datalogging, telemetry and virtual-switch capabilities are very rough and may need significant changes between now and release.

However, anyone who is willing to run the nightlies should report back whatever issues you find (ideally on bitbucket). I heavily rely on users to test the code and provide feedback, and the health of the next release will mostly be in your hands.

As noted above, there have been a lot of code churn lately, and stability is likely worse than usual. I would not recommend using the nightlies on anything you can't afford to fall out of the sky.

As I haven't been around for the past month, there's been no progress on stabilizing the code. Over the last few days, I've started chipping away at the bitbucket bug backlog. My focus is still on getting the release out as quickly as I can, so if you've been using the nightlies and have seen any problems, please file a ticket.
I am especially concerned about RandMetal's reboot issue ( bitbucket.org/PhracturedBlue/deviation/i...le-using-flysky-v911 ), as the debugger isn't helpful for his issue, and I haven't been able to reproduce it, so I have no idea what is going on. If anyone sees reboots with the nightlies, please send me the error (and elf) files