On Fri, Apr 26, 2024 at 7:20 PM Mark Thomas wrote:
>
> On 24/04/2024 17:52, Mark Thomas wrote:
>
>
>
> > My plan is to commit these changes to 11.0.x with the low risk parts
> > (e.g. new methods) back-ported. Then, once we can see what is left, we
> > can decide how quickly/slowly we want to
Mark,
On 4/26/24 13:17, Mark Thomas wrote:
On 24/04/2024 17:52, Mark Thomas wrote:
My plan is to commit these changes to 11.0.x with the low risk parts
(e.g. new methods) back-ported. Then, once we can see what is left, we
can decide how quickly/slowly we want to back-port the complete fix
On 24/04/2024 17:52, Mark Thomas wrote:
My plan is to commit these changes to 11.0.x with the low risk parts
(e.g. new methods) back-ported. Then, once we can see what is left, we
can decide how quickly/slowly we want to back-port the complete fix to
10.1.x and 9.0.x (the issue was reported
