Re: [Libreoffice-qa] ESC meeting agenda - Adding topic: Broken release process when fresh become still and when still become EOL'ed

On 29/01/2021 19:58, William Gathoye (LibreOffice) wrote: Ensuring there is no gap and the N-1 release doesn't EOL before N+2 is released Please read N+1 instead of N+2 obviously :P -- William Gathoye Hypertive volunteer for LibreOffice Proud member of The Document Foundation CM of LaMouette

Re: [Libreoffice-qa] ESC meeting agenda - Adding topic: Broken release process when fresh become still and when still become EOL'ed

On 28/01/2021 09:46, Michael Weghorn wrote: Unless anybody else suggests a different way to handle this, it IMHO certainly makes sense if you attend the ESC meeting today. (I've added that item to the agenda for now.) To @all I consider this problem solved iff the agreement reached during

Re: [Libreoffice-qa] ESC meeting agenda - Adding topic: Broken release process when fresh become still and when still become EOL'ed

On 28/01/2021 11:27, Florian Effenberger wrote: I think it is intentional that we always do have two parallel versions available for download, but it's something that might change as we are looking into the rolling release system, which makes this differentiation obsolete. Yes, exactly like

Re: [Libreoffice-qa] Starmath syntax hightlight

Respective ticket is https://bugs.documentfoundation.org/show_bug.cgi?id=138129 On 29.01.21 12:46, Dante Doménech wrote: The starmath syntax highlight first revision is now available here: https://gerrit.libreoffice.org/c/core/+/109639/21 I

Re: [Libreoffice-qa] ESC meeting agenda - Adding topic: Broken release process when fresh become still and when still become EOL'ed

On 28/01/2021 22.03, Jan-Marek Glogowski wrote: LO is regression plagued product. Yup. But honestly with the available resources, I don't see this changing in any time-frame, I can imagine. One IMHO main problem is, that we mainly have regression unit tests. So every change is almost guara