Mark,
On 3/5/24 07:18, Mark Thomas wrote:
On 27/02/2024 09:29, Christopher Schultz wrote:
Mark,
On 2/27/24 06:20, Mark Thomas wrote:
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't
On Tue, Mar 5, 2024 at 1:19 PM Mark Thomas wrote:
>
> On 27/02/2024 09:29, Christopher Schultz wrote:
> > Mark,
> >
> > On 2/27/24 06:20, Mark Thomas wrote:
> >> On 27/02/2024 10:57, Rémy Maucherat wrote:
> >>> On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
>
> All,
>
>
On 27/02/2024 09:29, Christopher Schultz wrote:
Mark,
On 2/27/24 06:20, Mark Thomas wrote:
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't much there to
justify
a March release. There
Mark,
On 2/27/24 06:20, Mark Thomas wrote:
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely
On Tue, Feb 27, 2024 at 12:20 PM Mark Thomas wrote:
>
> On 27/02/2024 10:57, Rémy Maucherat wrote:
> > On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
> >>
> >> All,
> >>
> >> When I look at the current change logs there isn't much there to justify
> >> a March release. There are a couple of
On 27/02/2024 10:57, Rémy Maucherat wrote:
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely that there is an actual issue to be fixed.
On Tue, Feb 27, 2024 at 10:12 AM Mark Thomas wrote:
>
> All,
>
> When I look at the current change logs there isn't much there to justify
> a March release. There are a couple of open bugs of which one looks
> likely that there is an actual issue to be fixed.
>
> That said, I'm unlikely to be in
All,
When I look at the current change logs there isn't much there to justify
a March release. There are a couple of open bugs of which one looks
likely that there is an actual issue to be fixed.
That said, I'm unlikely to be in a position to tag 11.0.x until w/c 11
March. The change log
Mark,
On 3/8/22 16:24, Mark Thomas wrote:
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time and we haven't had any bug reports.
However, it just
On 08/03/2022 23:54, Konstantin Kolinko wrote:
ср, 9 мар. 2022 г. в 00:24, Mark Thomas :
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time and we
ср, 9 мар. 2022 г. в 00:24, Mark Thomas :
>
> Hi all,
>
> I know I suggested skipping the March releases but I'd like to revisit
> that in light of two things.
>
> 1. The concurrency issue I fixed earlier today. [1]
> It has been present for a long time and we hav
On Tue, Mar 8, 2022 at 10:25 PM Mark Thomas wrote:
>
> Hi all,
>
> I know I suggested skipping the March releases but I'd like to revisit
> that in light of two things.
>
> 1. The concurrency issue I fixed earlier today. [1]
> It has been present for a long time and we hav
Hi all,
I know I suggested skipping the March releases but I'd like to revisit
that in light of two things.
1. The concurrency issue I fixed earlier today. [1]
It has been present for a long time and we haven't had any bug reports.
However, it just looks like a random timeout so users might
13 matches
Mail list logo
