Re: 4.2.0 release blockers

Hi Jim, Am 05.10.23 um 21:42 schrieb Jim Jagielski: On Oct 5, 2023, at 3:20 PM, Jim Jagielski wrote: On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic mailto:dam...@apache.org>> wrote: On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski mailto:j...@jagunet.com> > wrote:

Re: 4.2.0 release blockers

> On Oct 5, 2023, at 3:20 PM, Jim Jagielski wrote: > > > >> On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic > > wrote: >> >> On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski > > wrote: >> >>> >>> On Oct 1, 2023,

Re: 4.2.0 release blockers

> On Oct 4, 2023, at 2:12 PM, Damjan Jovanovic wrote: > > On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski > wrote: > >> >> >>> On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic wrote: >>> >>> 127154 and 127966 need to be looked at by a Mac developer. >>> >> >> Those

Re: 4.2.0 release blockers

Hello Dave, All, On Sun, Oct 01, 2023 at 09:11:14PM -0700, Dave Fisher wrote: > > On Oct 1, 2023, at 12:04 PM, Peter Kovacs wrote: > > > >> Am 01.10.23 um 13:44 schrieb Damjan Jovanovic: > >> Hi > >> > >> So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker > >> flags:

Re: 4.2.0 release blockers

Hi All, Am 01.10.23 um 21:04 schrieb Peter Kovacs: Am 01.10.23 um 13:44 schrieb Damjan Jovanovic: Hi So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker flags:

Re: 4.2.0 release blockers

On Wed, Oct 4, 2023 at 4:52 PM Jim Jagielski wrote: > > > > On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic wrote: > > > > 127154 and 127966 need to be looked at by a Mac developer. > > > > Those look pretty old. I should create a quick macOS 4.2.0 dev build for > testing > > Thank you Jim. While

Re: 4.2.0 release blockers

> On Oct 2, 2023, at 12:11 AM, Dave Fisher wrote: > > > Is there a step by step how to build AOO on these? Knowing the steps would > allow someone who is interested to try on their own Mac. > > Remind what version of macOS should be the minimum? My 11 year old iMac can > only be on

Re: 4.2.0 release blockers

> On Oct 1, 2023, at 7:44 AM, Damjan Jovanovic wrote: > > 127154 and 127966 need to be looked at by a Mac developer. > Those look pretty old. I should create a quick macOS 4.2.0 dev build for testing - To unsubscribe,

Re: 4.2.0 release blockers

Hi Keith, Am 03.10.23 um 21:48 schrieb Keith N. McKenna: Matthias Seidel wrote: Apart from the release blocker we need to get the translation process running again... At the moment we would only be able to release en-US. ;-) Regards,     Matthias Matthias; Where is the disconnect in the

Re: 4.2.0 release blockers

Matthias Seidel wrote: Apart from the release blocker we need to get the translation process running again... At the moment we would only be able to release en-US. ;-) Regards,    Matthias Matthias; Where is the disconnect in the translation process currently? Is it lack of translators,

Re: 4.2.0 release blockers

Sent from my iPhone > On Oct 1, 2023, at 12:04 PM, Peter Kovacs wrote: > >  >> Am 01.10.23 um 13:44 schrieb Damjan Jovanovic: >> Hi >> >> So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker >> flags: >>

Re: 4.2.0 release blockers

Hi All, Am 01.10.23 um 13:44 schrieb Damjan Jovanovic: Hi So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker flags: https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker of which there is 6: For 127731, I

Re: 4.2.0 release blockers

Am 01.10.23 um 13:44 schrieb Damjan Jovanovic: Hi So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker flags: https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker of which there is 6: For 127731, I found

4.2.0 release blockers

Hi So for 4.2.0, presumably we need to fix the bugs with 4.2.0_release_blocker flags: https://bz.apache.org/ooo/buglist.cgi?f1=flagtypes.name_id=251353=substring_format=advanced=---=4.2.0_release_blocker of which there is 6: For 127731, I found the problem yesterday (Microsoft's damned