Switch to main

[cristina-suteu]

PR Description

Switch to main from master in all references for adi repos.

PR Type

• Bug fix (a change that fixes an issue)
• New feature (a change that adds new functionality)
• Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

• I have conducted a self-review of my own code changes
• I have commented new code, particulary complex or unclear areas
• I have checked that I did not intoduced new warnings or errors (CI output)
• I have checked that components that use libiio did not get broken
• I have updated the documentation accordingly (GitHub Pages, READMEs, etc)

[Robin-Getz-Bose]

I hestitate doing this until we think we are close to getting 1.0 released (which I think strongly needs more automated testing, and thus the inclusion of iio-emu) - but looks good otherwise.

[dNechita]

I hestitate doing this until we think we are close to getting 1.0 released (which I think strongly needs more automated testing, and thus the inclusion of iio-emu) - but looks good otherwise.

I agree on the need for more testing. The inclusion of iio-emu will be done post 1.0 release.

[rgetz]

I agree on the need for more testing. The inclusion of iio-emu will be done post 1.0 release.

How do you do more programmatic testing and get and measure coverage without IIO-emu? To me - it’s a must have for 1.0 - letting users test and find bugs is not anything I would encourage.

[dNechita]

How do you do more programmatic testing and get and measure coverage without IIO-emu? To me - it’s a must have for 1.0 - letting users test and find bugs is not anything I would encourage.

One idea is to use the existing IIO-emu but I realize it won't be possible to measure coverage there. We will still have the testing though. I'll see if there's a way to quickly integrate iio-emu.

Regarding this PR, is there something preventing it from merging? It would fix the CI where a job tries to deploy the documentation, but the dir named "master" stands in the way.