We have 2.2.4, while latest stable is 2.3.1
for mga6 core release that is
It would be good if also put in backport in mga5 !
When done i will edit https://wiki.mageia.org/en/OwnCloud#Client_upgrading
lists.jjorge, luigiwalser, zombie_ryushuPriority:
There are "a ton of bugfixes", crash fixes, and lot more (i would suspect some security enhancement too)
(i could not find *nextcloud* client changelog but i guess it is same source still, + branding? )
Would be great if it could sneak in to mga6 release if not too late...
Yes. The major difference seems to be that NextCloud works with KDE 5 Plasma Wallet while OwnCloud Client seems to use the KDE 4 Wallet. Which means Plasma users can use the Pam KDE 5 Wallet module to authenticate if they are using Kerberos.
BTW, is it possible to make it use its own logo for the Plasma system tray- same it use for the program ( oOo ) ?
Currently at least all Nextcloud, ownCloud, and Dropbox clients confusingly use same symbol, while i.e Syncthing thanfully use its own.
Mageia 6 has been released and NextCloud has not been updated.
We are now at the end of july and every time i log in, a popup window invites me to upgrade to NextCloud 2.3.1 using my distrib package tools. But there is still no 2.3.1 available.
Mageia has a policy, it does not provide updates if they do not fix security or reproductible bugs.
If you read the client changelog at https://owncloud.org/changelog/desktop/ you will see there are lots of crashes in the first 2.3.x releases.
Still, we can provide it as a backport. If the maintainer agrees, I volunteers to do it.
We've updated owncloud-client to the latest stable before. Compatibility with web services is one of reasons we make exceptions to the policy, so I think this qualifies. You shouldn't need to do it as a backport.
I think it should have similar treatment as i.e Firefox.
Because of stability, compatibility, and security.
(and possibly the server part too)