HI Emmanuel, Thanks. I noticed that I have the required permissions to do that and I could have done it myself, but I wasn't sure when and who could do it.
There are also some issues that have been initially closed as fixed in 2.2.x, but later they were reopened to backport them to 2.0.x and 2.1.x branches. I think we can close them since the decision was made (wasn't it?) to not maintain 2.0.x and 2.1.x branches? Obviously if somebody requires these features contributions / back merges are always welcome... but somebody will have to pay the price for legacy version debt. There is at least one new issue that I have found and it will require a JIRA. Kind regards, Marcin On Tue, 20 Oct 2026 at 16:05, Emmanuel Lecharny <[email protected]> wrote: > Hi Marcin, > > > FTR I have closed the release for 2.2.10 in JIRA and all the associated > tickets. > > I also created a 2.2.11 versions for future issues. > > > I should have done that before the release. > > At some point, we should check all the opened tickets, and close them if > they are fixed, or associate them to a future version. It's actually a > bit of a mess, even if we only have 43 opened ticket ;-) > > > Emmanuel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
