I think there are two level of checks:
- Each PR (pull-up request) to merge developers code, requires 4 reviewers to accept it. It can't also be merged by the authoring developer himself. So usually multiple people review it before it gets accepted.
- People who do reviews also fly next, some keep tinkering with their aircraft, upgrading old, getting new. Coming up with ideas or always are on next, so it's tested by usage.
Last time I build next was Saturday (2 days ago), just to update 2 micro quads and 1 bigger quad, but went to fly with bigger one to test fpv hardware upgrade.
If you want to help, would be good if you could familiarize yourself with git
git add remote somedev http://bitbucket.com/somedev/librepilot
git fetch somedev
git branch -a
git checkout somedev/featureToReview
# here usual make clean ; make ....
You could also familiarize yourself with git merge or git rebase commands which allow you to combine next with someones work locally.
This is pretty good tutorial which if followed step by step will make you good at using git
https://www.atlassian.com/git/tutorialsThen you can go to bitbucket website and look for PR (pull-up requests), test them out, give comments.
For already merged code, usual features are stable and well tested, but if you use something unusual, and notice a problem. You can try fixing it or reporting it to devs.
How to build software from git for different operating systems you can find on Wiki for example for Linux
https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/57671696/Linux+-+Building+and+Packaging