It's not correct to close the issue which affects version 3 as fixed if fix does not affect version 3. Isn't it? Let's backport the fix to versio 3 as well.

It's not correct to close the issue which affects version 3 as fixed if fix does not affect version 3. Isn't it?

That happens a lot. Isn't it?

It's not correct to close the issue which affects version 3 as fixed if fix does not affect version 3. Isn't it?

That happens a lot. Isn't it?

No. It should not happend. It's a regression and an application working on 2.5 cannot work properly on 3.0.

On 10/5/21 2:43 PM, Adriano dos Santos Fernandes wrote: It's not correct to close the issue which affects version 3 as fixed if fix does not affect version 3. Isn't it? That happens a lot. Isn't it?
Yes. Sometimes backporting a fix means too many changes in code of old version. One can get 3.99 instead 3.0 in that case :)

I'm not so sure about that. 3.99 has a lot of other changes. It might be possible to use it for testing, test migration but it's not always easy just replace 3.0 by 3.99. Especially in enterprise. In this case let's 3.0 version as unsupported.

And fixing it in 3.0 would much probably means introduce another bug fixed in 3.0.

It's why the regex engine was completely changed to re2 in 4.0.

Backport of that is too much for 3.0.

I see and would agree if there is a workaround. But there are several cases when there is no error. Server just returns wrong result. IMO it is too much for server usage )

Let's backport re2 to 3.0 :) We are ready to test before merging.