This time there will be a RC (release candidate) and a freezing period first to make sure there won’t be any newly introduced problems when the final release is tagged a bit later. In the past one release had to be skipped because a new critical bug crept in unnoticed with last moment changes. Now there won’t be last moment changes unless (older) critical bugs are found and fixed within the freezing period. But this means that the RC still needs testing to make sure there aren’t critical bugs, so go ahead and try.
Jenkins-440 64 bit seems fine after a quick check.
It seems a fixed pattern that after months of rock solid stability a critical bug pops up just before a release freeze. Probably developers rushing commits to grab the cycle
Yep, I’ve been using it quite a bit the last two(2) days with only one quirk.
My mouse-wheel zoom got Hyper Sensitive in PcbNew one time. Only two clicks for full zoom from one extreme to the other; and it wasn’t the mouse as Escheema was also open and the mouse function there was normal. Closing and reopening PcbNew resolved the issue.
Flatpack is not one of the officially supported options (There are 4 official linux options: Ubuntu, Debian, Fedora and Arch). It is provided by some volunteer outside the core team so it is to be expected that it can sometimes take some time till it is released. (Or you know the volunteer that provided it moved on in live)
Packaging is done by volunteers, not by the development team. As far as I have understood, packages for the officially supported platforms are waited for before releases are announced. Not others. So, nobody has done it.
Unfortunately it’s a problem that we list them on the website which just sets false expectations for users I removed one distro from the website recently because they haven’t updated from the 5.0.x series for over a year.