Description: MAR updates will be the default on Linux and Windows in 25.2 as per https://bugs.documentfoundation.org/show_bug.cgi?id=68274#c86 Sadly the tender (https://blog.documentfoundation.org/blog/2021/08/03/tender-to-implement-autoupdater-202108-01/) which was used to add MAR to Linux / Windows did mention macOS, but that part never got implemented which is a bit odd, since money was spent and the tender does mention macOS just as it mentions Linux, Windows. This feels as if a new tender is needed to bring macOS on par with other OS implementations of the updater. Users would benefit hugely from having a reliable and easy updater. I know many less tech savvy users that are not using the MAS verion of LibreOffice and are having a hard time updating LibreOffice (they mostly don't). Steps to Reproduce: No repro steps needed. There is no MAR updater on macOS. Actual Results: No MAR updater Expected Results: macOS implementation on par with Linux and Windows, which will default to MAR updater in 25.2. Reproducible: Always User Profile Reset: No Additional Info: N/A
(In reply to steve from comment #0) > Description: > MAR updates will be the default on Linux and Windows in 25.2 as per > https://bugs.documentfoundation.org/show_bug.cgi?id=68274#c86 > > Sadly the tender > (https://blog.documentfoundation.org/blog/2021/08/03/tender-to-implement- > autoupdater-202108-01/) which was used to add MAR to Linux / Windows did > mention macOS, but that part never got implemented which is a bit odd, since > money was spent and the tender does mention macOS just as it mentions Linux, > Windows. From the said blog entry [quote] … Mandatory requirements • The solution has to work on _all_ currently LibreOffice-supported Windows, Linux and macOS versions. … [/quote] This very 1st mandatory requirement _includes_ macOS, not excludes it! > This feels as if a new tender is needed to bring macOS on par with other OS > implementations of the updater. Yes. But as I understand the blog post, it shouldn't be actually necessary, because Bug #68274 already catches it also for the macOS platform. To exclude macOS and simply close #68274 seems to me prematurely, the work is only half done, the bug only partially fixed in my point of view. Bug #68274 should be reopend and stay open, until the issue is resolved and fixed for ALL platforms and so also for the macOS platform (and so be in line with the very first one of the published mandatory requirements).
There is no need for a new tender, the people who took the tender should complete the job at first place. This bug report should also be closed, as asking for a new tender sounds like justifying the uncompleted work done in the first one.
(In reply to Emir Sarı from comment #2) > the people who took the tender should > complete the job at first place. This bug report … > asking for a new tender sounds like justifying the uncompleted work done in > the first one. +1
Hmm, not sure the TDF tender was taken up/executed. Rather work on Mozilla ARchive packaged incremental updates thus far was simply volunteered by Nathan Yee, Markus Mohrhard, Stephan Bergmann with TDF infra support.
For the avoidance of doubt: allotropia did **not** implement the Windows auto-updater via the TDF tender. To the best of my knowledge, that tender was never awarded.
(In reply to Thorsten Behrens (allotropia) from comment #5) > For the avoidance of doubt: allotropia did **not** implement the Windows > auto-updater via the TDF tender. To the best of my knowledge, that tender > was never awarded. Thank you very much for this clarification.
Thorsten: thanks for the clarification also from my side and sorry for causing confusion. It is a bit hard to understand a tenders status if the blog post is not updated. Unsure what a better format to keep track of tenders would be.