ElderDryas wrote:In that case I was wonder what Slack/Salix would do, upgrade to 4.8 (as the more recent and stable version) or 4.10 (as the most recent and maybe stable).
There is no general one fits them all rule. It depends entirely on the application. But I for my part always package the latest version unless it has stability problems or is severly broken (like doesn't build on that Salix version). Slackware is generally a bit more conservative. But this makes sense in many cases for packages likely to have issue and which are widely deployed. Therefor a relatively likely issue would have a great impact and would affect pretty much every user. Some examples would be kernel, Xorg, Xfce, gtk libs, ... That's not really the case for any of my packages.#
Generally speaking for normal applications, which are not built on by many parts of the system, you can always expect the latest version AT the time of the repository freeze. Unless of course there are problems. Don't expect the latest for core system packages like udev, kernel, glibc, ... For other basic but not as crucial packages it depends a lot on the individual project and how stable their releases generally are.
That's my 5 cents. Other devs might have a bit different opinions. But I think as recent as easily possible makes sense (no old bugs fixed since ages by upstream, new features, ...). But not at any cost. Still talking about current before the freeze of course.