Hi, I see, there are Mate desktop 1.8 in Mageia 5 by tarakbumba ( Atilla ÃNTAÅ ) Can you put for mageia 4 backport please ? thank you so much :p Reproducible: Steps to Reproduce:
Our backports policy doesn't allow that to happen. And we are not going to kill our QA :)
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => WONTFIX
Okay but version 1.6 is end of life Every new version, last stable come EOF : http://wiki.mate-desktop.org/dev-doc "Only one stable release is supported at a time. Once a new stable release is made, it immediately obsoletes the previous stable release." So Mageia 4 is new version but with Mate 1.6 is obsoletes thank you.
URL: (none) => http://www.mageialinux-online.org/forum/topic-17820+mate-et-les-mises-a-jour-de-maintenance.php
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)
Backport policy for Mageia (and the others : OpenSuse or Debian for example) do not allow this kind of update, even in backports. KDE 4.12 is a exception because KDE 4.11 and higher are LTS and there's only apps that are going to be updated. That's the point : backports is used to update applications, not an entire DE. We can have the same example with Gnome DE, one version is supported at a time, in a couple of weeks, this will be Gnome 3.12. Mageia 4 is running 3.10, but it is certain that we'll keep Gnome 3.10. (same for mageia 3 who had GNome 3.6 in his repos even if GNome 3.8 was released before Mageia) And the other thing is that the packager will have to maintain the official one (1.6 in mga4), the backports one (1.8 mga4) and the cauldron one (1.8 mga5). To my mind, not a good idea, sorry :/
CC: (none) => guillaume.ber17
first see if maintainer is ok, and see if qa can tell about policy
Keywords: (none) => TriagedCC: (none) => qa-bugs, tarakbumbaComponent: New RPM package request => BackportsSource RPM: (none) => task-mate
Well, packaging is not a problem. The problem is maintaining them as Guillaume suggested. There are some serious issues with backporting MATE 1.8. Devs dropped mate-keyring, mate-doc-utils, mucharmap and some other applications. So, backporting Mate 1.8 is would bring problems rather than providing goodies. Also, our MATE 1.6 already benefited MATE 1.8 bug fixes and some improvements via cherry-picked patches. As a result; unfortunately i do not want to break policy, to deal with bugs from backports and to backport MATE 1.8 into Mageia 4 officially. May be an unofficial one... But may be...
Backports are causing issues with rpmdrake at the moment. The backport media was cleared until it can be addressed. A DE wouldn't be considered a suitable thing to backport most likely. It should be leaf packages only. Having said that, in the past, we have had kde and xfce updates issued through update medias. If you wish to issue an update I would suggest that would be the way to do it. Again though it would not have to cause any regressions on a stable system. If the current Mate is unsupported, as maintainer, this is something you might want to do.
(In reply to claire robinson from comment #6) > Backports are causing issues with rpmdrake at the moment. The backport media > was cleared until it can be addressed. > > A DE wouldn't be considered a suitable thing to backport most likely. It > should be leaf packages only. > > Having said that, in the past, we have had kde and xfce updates issued > through update medias. If you wish to issue an update I would suggest that > would be the way to do it. Again though it would not have to cause any > regressions on a stable system. > > If the current Mate is unsupported, as maintainer, this is something you > might want to do. There are problems with MATE 1.8 for us. Like i said mate-keyring, libmate-keyring, mate-bluetooth, mate-doc-utils etc. have been deprecated. Also, many apps like mate-image-viewer, mate-file-manager* etc. renamed. An update or backport might (and i'm sure will) break our current MATE Desktop. But i'm rebuilding MATE 1.8 branch for my Mageia 4 install and try to address possible breakages if i push them to backports/updates. My main concern is what QA team will do with a whole desktop updates? You and your team working hard and this update will bring much work to you. I also ask this to other devs.
After a little discussion at Dev-Ml it has been revealed that some other applications will be badly affected if MATE 1.8 is introduced either via backports or via updates into Mageia 4. So, i decided to maintain 1.6 series with only cherry picked bug fixes from upstream stable branch and not to provide 1.8 in Mageia 4 officially. Sorry. As MATE maintainer i'm closing this bug report.
Status: REOPENED => RESOLVEDResolution: (none) => WONTFIXAssignee: bugsquad => tarakbumba
Okay thank you Atilla for feedback :(