Íñigo Huguet de5cce5972 release.sh: stop doing "-dev" releases on stable branches ... Note: here I refer to the numbers in a version as MAJOR.MINOR.MICRO. Having stable and development releases do make sense for the MINOR version, because we maintain separate branches for them and they evolve separately. We have 1.47.z where we put all the changes so anyone can pick the latest development release and test it. At the same time, we have 1.46.z with the latest stable released version. However, it does not make sense to have 1.46.2 and 1.46.3-dev because the latter is not a development version. It is identical to 1.46.2, only the version number has been bumped, there are no changes to test. When we add commits, we will be actually testing 1.46.3-dev + some commits, which is exactly the same as testing 1.46.2 + some commits. So, basically, someone can use the releases of a development BRANCH, like 1.47.4, to test the development version of NM. But using a development MICRO version is exactly the same as using a non-development one. From now on, we will just increment the MICRO version each time we do a release on a stable branch and won't create the '-dev' tag. Update release.sh to do it this way. (cherry picked from commit 8eb00c0991)		2024-05-31 13:04:20 +02:00
..
alpine	contrib/packages: install pexpect	2022-06-30 10:20:44 +02:00
art/logo
debian	contrib: add libpsl-dev to debian requirements	2023-09-13 16:29:01 +02:00
editors
fedora	release.sh: stop doing "-dev" releases on stable branches	2024-05-31 13:04:20 +02:00
scripts	gitlab-ci: ignore autotools deprecation	2024-05-09 12:00:47 +02:00