On Fri 2020-06-26, Dominique Leuenberger / DimStar wrote:
Tomas and I just had a quick discussion about this and agreed to move forward with RCs (this is not the first beta of LO we had in TW - but apparenly one of the betas causing more trouble).
Thank you for looking into this, Dominique. Based on my experience I second that switching in the LibreOffice RC phase may be the better trade off. There's at least two serious regressions that I found and reported upstream in current LibreOffice betas that were addressed already. And having a stable release available via the distro in parallel to upstream dev-builds has helped me reproduce, isolate, and report many issues upstream. On the other hand, Tumbleweed is a rolling distribution that aims to not break things (totally), but accepts calculated risk, so going for an RC appears reasonable.
Of course we have no guarantee that if you were not finding the bugs, if they'd be fixed in the final release :)
My personal approach recently is using a dev-build (beta build) of LibreOffice by default, and reverting to what Tumbleweed provides if I run into a problem. So Tumbleweed provides my safety net. :-)
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1173404 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1173409 [3] https://bugzilla.opensuse.org/show_bug.cgi?id=1173410 Would you mind filing those (and future ones) directly in LO's bug tracker? This could shorten the communication by a bit.
I have filed the first upstream after checking that it was not there yet (incl. looking for reports by Atri) and reproducing it - Atri, I copied you on that report so that you can follow the progress. And I closed the openSUSE report as RESOLVED UPSTREAM. I'll be tackling the next in the coming hours. - Atri, boo#1173410 reproduces in a slightly restricted manner, but it generally does. Gerald -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org