I see that MATE 1.28 has landed in Tumbleweed, but will it be included in Leap 15.6?
MATE 1.26 released in August 2021 and it would be a shame if Leap users had to wait another year for a new release.
Why oh why?
I’m sorry?
You declare it being “a shame”. I ask why this verdict.
It’s just an expression. I’m just stating that it would be unfortunate if MATE stays on the old version for another year. Current version is in a rather buggy state.
I have no insider info, but I still see 1.26 in Leap 15.6 repo, for instance
mate-control-center
1.28 apparently landed in TW on April 9, but the code freeze for Leap 15.6 already happened on April 17 ( see mailinglist and roadmap ), likely too little time to build / test / fix an entire desktop environment… so my guess is you will still see 1.26 in the Leap 15.6 release.
I don’t know if anybody will have the time to do an update afterwards, but I doubt it (no SUSE employees working on Mate and the few community members focused on Tumbleweed AFAIK).
Not a nice one for the devs that are doing their best to deliver an integral tested Leap version.
“It’s a shame” has been a mild expression of disappointment, in the USA at least, for a century or more, used by people who don’t cuss or swear.
OK, let us see this as a cultural difference in a multi-cultural forum.
In any case I also doubt that, 15.6 already being beta, they will start the integrated testing anew with new software versions. There is of course a closing date, but I do not know where to find that.
And 1.28 has its problems too
https://forums.opensuse.org/t/tumbleweed-mate-desktop-broken-in-april-10-update/174159
another reason to not include it in Leap 15.6 initial release.
Actually, MATE is fine in Tumbleweed once you install dconf-editor which was missing from the requirements and fix the 2 spelling errors.
I suspect it will be added to 15.6 in some update, once it passes QA.
That would not be according to the Leap philosophy. Versions are not changed during the lifetime of a Leap Version, security fixes are back-ported. This is the “stability” of Leap. A user will not get an unwanted surprise by getting a changed user interface, output, action of a program, just because of a normal update (security and recommended) of a Leap.
The Leap folks did update from 1.24 to 1.26 in the past.
Lots of versions get updated in the middle and not backported - Firefox-esr, Libreoffice, and wine all come to mind.
@larryr sure it happens, especially if CVE related. RC1 is about to drop. Maybe in the respin in 6 months or so…
My experience is that the basic system inherited from SLE (e.g. kernel, systemd…) gets no version bump and security fixes are backported.
User apps (e.g. Firefox) get version bumps.
Not sure about an entire DE, I saw no version bumps to Gnome in Leap (and I switched to TW when needing one for HW compatibility 
)
Long time mate user. I have mate 1.28 in tumbleweed vm and 1.26 in leap 15.5 on host. I don’t see any dramatic changes between 1.26 and 1.28 of mate so I won’t get very concerned about not getting change in leap.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.