Re: [QGIS-Developer] Issue with future 3.22 LTR ? (a.k.a missing backports to 3.22)

Ok, well that's reassuring :-) Thanks for the clarifications ! Cheers, Olivier Le ven. 10 déc. 2021 à 09:09, Etienne Trimaille a écrit : > As Harissou said, the PR was created before the 3.22 branch, so the label > "backport release-3_32" was not created at that time. > > Le jeu. 9 déc. 2021

Re: [QGIS-Developer] Issue with future 3.22 LTR ? (a.k.a missing backports to 3.22)

As Harissou said, the PR was created before the 3.22 branch, so the label "backport release-3_32" was not created at that time. Le jeu. 9 déc. 2021 à 15:54, DelazJ a écrit : > Hi Olivier, > > Yes, backporting to 3.16 implies backport to 3.22. And I think the PR you > point here is more about for

Re: [QGIS-Developer] Issue with future 3.22 LTR ? (a.k.a missing backports to 3.22)

Hi, I confirm it's completely about forgetting. When I backported in 3.16 (queued ltr backports), I believed the backport in 3.22 was already done which was not the case. Thank you for fixing this. Kind regards, Julien > Hi Olivier, > > Yes, backporting to 3.16 implies backport to 3.22. And I t

Re: [QGIS-Developer] Issue with future 3.22 LTR ? (a.k.a missing backports to 3.22)

Hi Olivier, Yes, backporting to 3.16 implies backport to 3.22. And I think the PR you point here is more about forgetting. The PR itself is opened during 3.22.0 dev cycle and merged few days after release, so easier to forget to add the label. And the list of missing PRs should actually be https:/

[QGIS-Developer] Issue with future 3.22 LTR ? (a.k.a missing backports to 3.22)

Hi all ! There's something I don't completely understand with the current branches/releases process and which to me looks like a major issue (came across it while checking the status of a recently merged bugfix PR#45521 ). That fix was merged to master wit