Re: The way to 4.2.0

2025-01-13 Thread Jim Jagielski
> On Jan 11, 2025, at 1:23 PM, Matthias Seidel > wrote: > > Hi Jim, > > Am 30.12.24 um 11:06 schrieb Jim Jagielski: >> >>> On Dec 30, 2024, at 12:03 AM, Damjan Jovanovic wrote: >>> >>> On Mon, Dec 30, 2024 at 1:07 AM Damjan Jovanovic wrote: >>> - Another "regression" (Bugzilla seems

Re: The way to 4.2.0

2025-01-11 Thread Matthias Seidel
Hi Jim, Am 30.12.24 um 11:06 schrieb Jim Jagielski: On Dec 30, 2024, at 12:03 AM, Damjan Jovanovic wrote: On Mon, Dec 30, 2024 at 1:07 AM Damjan Jovanovic wrote: - Another "regression" (Bugzilla seems to be down?) which is Windows-only, and has a known but ugly workaround - we leak the li

Re: The way to 4.2.0

2024-12-30 Thread Jim Jagielski
> On Dec 30, 2024, at 12:03 AM, Damjan Jovanovic wrote: > > On Mon, Dec 30, 2024 at 1:07 AM Damjan Jovanovic wrote: > >> - Another "regression" (Bugzilla seems to be down?) which is Windows-only, >> and has a known but ugly workaround - we leak the library handle like we >> did before (and st

Re: The way to 4.2.0

2024-12-29 Thread Damjan Jovanovic
On Mon, Dec 30, 2024 at 1:07 AM Damjan Jovanovic wrote: > - Another "regression" (Bugzilla seems to be down?) which is Windows-only, > and has a known but ugly workaround - we leak the library handle like we > did before (and still do on 4.1.x), instead of releasing it properly. > > This is that

Re: The way to 4.2.0

2024-12-29 Thread Dave Fisher
> On Dec 29, 2024, at 5:17 PM, Aivaras Stepukonis wrote: > >> - Another "regression" (Bugzilla seems to be down?) which is Windows-only, >> and has a known but ugly workaround - we leak the library handle like we >> did before (and still do on 4.1.x), instead of releasing it properly. > This o

Re: The way to 4.2.0

2024-12-29 Thread Aivaras Stepukonis
- Another "regression" (Bugzilla seems to be down?) which is Windows-only, and has a known but ugly workaround - we leak the library handle like we did before (and still do on 4.1.x), instead of releasing it properly. This one, if I read it correctly, I can confirm. It is rather bad. As soon as f

Re: The way to 4.2.0

2024-12-29 Thread Damjan Jovanovic
On Sun, Dec 29, 2024 at 9:12 PM Arrigo Marchiori wrote: > Hello all, > > On Sun, Dec 29, 2024 at 10:01:56AM +, Peter kovacs wrote: > > > Hi all. > > > > So let's discuss blockers of 4.2.0. > > > > I am only aware of translations 4.2.0 as a real blocker. > > There is a nasty, repeatable crash

Re: The way to 4.2.0

2024-12-29 Thread Arrigo Marchiori
Hello all, On Sun, Dec 29, 2024 at 10:01:56AM +, Peter kovacs wrote: > Hi all. > > So let's discuss blockers of 4.2.0. > > I am only aware of translations 4.2.0 as a real blocker. There is a nasty, repeatable crash of Impress under Windows. I tried to look into it some time ago but I fail

Re: The way to 4.2.0

2024-12-29 Thread Dave Fisher
> On Dec 29, 2024, at 2:49 AM, Matthias Seidel > wrote: > > Hi Peter, > > Am 29.12.24 um 11:01 schrieb Peter kovacs: >> Hi all. >> >> So let's discuss blockers of 4.2.0. >> >> I am only aware of translations 4.2.0 as a real blocker. > We still have other blocker to fix, but yes, translatio

Re: The way to 4.2.0

2024-12-29 Thread Matthias Seidel
Hi Peter, Am 29.12.24 um 11:01 schrieb Peter kovacs: Hi all. So let's discuss blockers of 4.2.0. I am only aware of translations 4.2.0 as a real blocker. We still have other blocker to fix, but yes, translation is the *real* blocker. Afaik it is unclear if our translations are still complet

The way to 4.2.0

2024-12-29 Thread Peter kovacs
Hi all. So let's discuss blockers of 4.2.0. I am only aware of translations 4.2.0 as a real blocker. Afaik it is unclear if our translations are still complete. So we need one time to convert the us sdf from the nightly build server (hope it builds) to PO format and then convert the translated