Dear Tumbleweed users and hackers,
This has been a week in which we focused a little bit less on Staging, as it was SUSE HackWeek. ‘Less’ does not mean we ignored it of course. We still managed to release 4 snapshots (0318, 0319, 0320, and 0321) during this week.
The changes delivered this week included:
- transactional-updates 3.2.2
- KDE Plasma 5.21.3
- Perl 5.32.1
- GTK+ 3.24.27
- SQLite 3.35.2: fixes an issue in combination with Tracker timing out
The future, near or far, will bring those updates:
- SELinux 3.2
- GNOME 40
- MicroOS Desktop – GNOME-based
- Python 3.9 modules: besides python36-FOO and python38-FOO, we are testing to also shop python39-FOO modules; we already have the interpreter after all. Python 3.8 will remain the default for now.
- UsrMerge is gaining some traction again, thanks to Ludwig for pushing for it
- GCC 11 as the default compiler
[…] "This has been a week in which we focused a little bit less on Staging, as it was SUSE HackWeek. ‘Less’ does not mean we ignored it of course. We still managed to release 4 snapshots (0318, 0319, 0320, and 0321) during this week." http://dominique.leuenberger.net/blog/2021/03/opensuse-tumbleweed-review-of-the-week-2021-12/ […]
[…] http://dominique.leuenberger.net/blog/2021/03/opensuse-tumbleweed-review-of-the-week-2021-12/ […]
Yeah, I’d call it “focused a lot less on Staging”. You are now 5 releases behind in regards to kernels, stuck on 5.11.6 as of the 0321 snapshot. Their are breaking changes for some AMD hardware as of that kernel, they’ve already been resolved by one or your own kernel devs, sent upstream, pulled into one of the 5.12 rc’s, marked for backporting into 5.11, pulled in, and released. But you have nothing beyond 5.11.6 even staged apparently.
Your devs are great. Staging, not so much. You are too quick to pull in new major releases (even Arch Linux is more cautious), then you’re way too slow iterating the minor point releases where the real work happens to fix upstream’s constant regressions.
And in this case, your automated QA/CI processes that tend to slow things down for a rolling release distro didn’t even catch the bug in question.
Thanks for your comment.
There is one thing to take notes though: we can only stage, what the maintainers submit for Integration. So if the devs fixed it but did not create a submission to include stuff in Tumbleweed, i and sorry to say, that is on them.
If it were stuck in a staging i would be accepting taking the blame.
That
OpenQA being based on qemu is known to have some shortcomings when it comes to hardware/ driver bugs.