CubicSDR VS semver

Looks like I got cubic sdr executable cubicsdr_v0_2_6a_win64 from https://github.com/cjcliffe/CubicSDR/releases/tag/0.2.4.

There is loads of software that will work such as SDR++, GQRX, CubicSDR, and SDRangel just to name a few. For HD radio reception, there is nrsc5. Nrsc5 only works with an rtl-sdr, so you will need one if you want to receive HD radio.

CubicSDR and GQRX both work on my M1 Mac. I installed GQRX using homebrew, CubicSDR was downloaded from Github (https://github.com/cjcliffe/CubicSDR/releases/tag/0.2.5). Both are the x86_64 versions and run under the emulation layer provided by Mac OS.

CubicSDR

Be aware that 3.1.5 enables EGL by default and, if your application uses GLX, you're going to have problems: https://github.com/cjcliffe/CubicSDR/issues/886

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: