Bug 625838 – MATE 1.18 stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pacho Ramos 2017-07-21 10:23:07 UTC]

Current stable is 1.12 and has dependencies on many obsolete libraries (like atril and old webkit-gtk). I was looking into suggesting to stabilize a newer atril, but it seems it would be better to stabilize a newer full MATE desktop for better integration probably. Are there any plans to stabilize a newer MATE in the near future?

Thanks!

[Comment 1 Stephan Litterst 2017-09-30 05:52:44 UTC]

How can I help to stabilize mate 1.18?

[Comment 2 Ettore Di Giacinto (RETIRED) 2017-10-05 15:52:10 UTC]

Upstream declares 1.16 as stable and 1.18 unstable, and i have to agree on that,  1.18 is still buggy and have quite lot of outstanding bugs (upstream issue tracker). After discussing this with NP, we are going to follow upstream, thus stabilize 1.16 (very soon), and finally drop the old 1.12 from tree.

[Comment 3 Stephan Litterst 2017-10-11 09:35:55 UTC]

"very soon" could be interpreted in a lot of different ways. 
What is *your* definition of "very soon"?

[Comment 4 Joakim Tjernlund 2017-10-11 09:40:33 UTC]

(In reply to Ettore Di Giacinto from comment #2)
> Upstream declares 1.16 as stable and 1.18 unstable, and i have to agree on
> that,  1.18 is still buggy and have quite lot of outstanding bugs (upstream
> issue tracker). After discussing this with NP, we are going to follow
> upstream, thus stabilize 1.16 (very soon), and finally drop the old 1.12
> from tree.

And Gentoo is lagging behind MATE 1.18, there are newer releases upstream
for MATE 1.18

[Comment 5 Pacho Ramos 2018-04-18 09:24:47 UTC]

Looking to the blockers for Mate 1.16 stabilization (bugs solved in 1.18), I am not sure if even 1.18 considered as "unstable" would still be a better candidate than 1.16 :/

[Comment 6 Pacho Ramos 2018-06-16 15:29:55 UTC]

*** Bug 654806 has been marked as a duplicate of this bug. ***

[Comment 7 kuzetsa CatSwarm (kuza for short) 2018-06-17 02:38:40 UTC]

(In reply to Pacho Ramos from comment #5)
> Looking to the blockers for Mate 1.16 stabilization (bugs solved in 1.18), I
> am not sure if even 1.18 considered as "unstable" would still be a better
> candidate than 1.16 :/

     Thu Jun  8 00:40:31 2017 >>> mate-base/mate-common-1.18.0
     Thu Jun  8 00:45:20 2017 >>> x11-themes/mate-icon-theme-1.18.2
     Thu Jun  8 00:46:09 2017 >>> x11-themes/mate-backgrounds-1.18.0
     Thu Jun  8 00:47:39 2017 >>> mate-base/mate-desktop-1.18.0
     Thu Jun  8 00:51:40 2017 >>> dev-libs/libmateweather-1.18.0

[...]

^ according to genlop I've literally used mate 1.18.x for over a year.

EVERY bug 1.12.x, 1.14.x, or 1.16.x is fixed on 1.18.x

(or more specifically: the ones which personally caused me problems)

[Comment 8 Tango 2018-07-01 17:00:08 UTC]

(In reply to Pacho Ramos from comment #5)
> Looking to the blockers for Mate 1.16 stabilization (bugs solved in 1.18), I
> am not sure if even 1.18 considered as "unstable" would still be a better
> candidate than 1.16 :/

Second that: I would prefer 1.18 get stabilized over 1.16. Been working with 1.18 on my 2 of my workstations for a few months now and have no major issues. I will be updating to 1.18 on my other 2 systems some time this coming week as 1.12 has gotten kinda stale.

Would also like to see 1.20 moved into portage for testing purposes.

[Comment 9 Mart Raudsepp 2018-09-08 16:33:24 UTC]

Lets say that this is some heavy maintainer timeout, or rather that I had OK to prep stable list for 1.18 from mudler that he can ACK then, but I'm CCing arches immediately due to not getting an automated repoman sanity check otherwise.
mudler also said he knows no big issues with 1.18 over the rest and has been using it for a long time, just too busy with non-gentoo things. Lets just proceed with stabilizing please.

[Comment 10 Thomas Deutschmann (RETIRED) 2018-09-09 23:57:39 UTC]

x86 stable

[Comment 11 Mikle Kolyada (RETIRED) 2018-09-10 08:50:18 UTC]

amd64 stable but I postponed the push till evning, but it should be fired till the end of this day.

[Comment 12 Mikle Kolyada (RETIRED) 2018-09-10 16:20:51 UTC]

finally stable