This moves CHIRP to use a proxy for repeaterbook at chirpmyradio.com
to reduce load on the repeaterbook API and improve performance for
our users.
Also, don't run the network tests in CI as they're less important
now and also their failing probably has nothing to do with the patch
being submitted.
The share of python3-uncompliant drivers has dropped to such a small
fraction that I've forgotten to enforce that new drivers be added to
the matrix.
So, at this point, it's time to flip the whitelist to a blacklist and
just mark the drivers that haven't been tested. This removes the
matrix and generation script, content from the makesupported target,
and instructions from the PR template. It replaces those with a simple
list of drivers in tests/py3-untested-drivers.txt
Almost all the drivers in the tree now opt out of the byte-compat
behavior. The default has been flipped, so we can remove that from
all those drivers and remove it from the PR template so people don't
have to think about it anymore.
Move everything to Jammy 22.04, but keep a driver job on 20.04 to
make sure we don't regress. 20.04 is the last release where it is
feasible to work on both master and py3, so we should try to avoid
breaking support there for the interim.
If we fail to run makesupported, we will not touch anything, but
return nonzero, which will try to git commit, which will fail because
nothing is changed. Just ignore that and push the PR anyway so we have
something to work from.
If we fail to run makesupported, we will not touch anything, but
return nonzero, which will try to git commit, which will fail because
nothing is changed. Just ignore that and push the PR anyway so we have
something to work from.
If we fail to run makesupported, we will not touch anything, but
return nonzero, which will try to git commit, which will fail because
nothing is changed. Just ignore that and push the PR anyway so we have
something to work from.
