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

2021-12-14 Thread Olivier Dalang 
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 à 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 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://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3A%22backport+queued_ltr_backports%22+-label%3A%22backport+release-3_22%22+merged%3A%3E2021-10-21
>> since anything merged before 22/10/2021 is automatically in 3.22. Finally,
>> there's no that much leftover PRs, so I think everybody is OK with your
>> logic.
>>
>> Regards,
>> Harrissou
>>
>> Le jeu. 9 déc. 2021 à 15:29, Olivier Dalang  a
>> écrit :
>>
>>> 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 with the `backport queued_ltr_backports`
>>> label, but without `backport release-3_22`.
>>>
>>> As far as I understand, this means it will be available in 3.24 (master)
>>> and in 3.16 (after some quarantine), but not in 3.22. Still if I understand
>>> correctly, 3.22 is our future LTR, meaning that LTR users will at some
>>> point upgrade from 3.16 to 3.22. Does that mean that the bug they have seen
>>> fixed in 3.16 will be reintroduced in 3.22 ?
>>>
>>> The following filter shows many other PRs backported to 3.16 but not
>>> 3.22 :
>>> is:pr label:"backport queued_ltr_backports" -label:"backport
>>> release-3_22"
>>> 
>>>  (same
>>> search should also be done with label `backport release-3_16`)
>>>
>>> Shouldn't backporting to 3.16 always imply backporting to 3.22 ? Or am I
>>> missing something ?
>>>
>>> Cheers !
>>>
>>> Olivier
>>> ___
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

2021-12-10 Thread Etienne Trimaille 
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 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://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3A%22backport+queued_ltr_backports%22+-label%3A%22backport+release-3_22%22+merged%3A%3E2021-10-21
> since anything merged before 22/10/2021 is automatically in 3.22. Finally,
> there's no that much leftover PRs, so I think everybody is OK with your
> logic.
>
> Regards,
> Harrissou
>
> Le jeu. 9 déc. 2021 à 15:29, Olivier Dalang  a
> écrit :
>
>> 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 with the `backport queued_ltr_backports`
>> label, but without `backport release-3_22`.
>>
>> As far as I understand, this means it will be available in 3.24 (master)
>> and in 3.16 (after some quarantine), but not in 3.22. Still if I understand
>> correctly, 3.22 is our future LTR, meaning that LTR users will at some
>> point upgrade from 3.16 to 3.22. Does that mean that the bug they have seen
>> fixed in 3.16 will be reintroduced in 3.22 ?
>>
>> The following filter shows many other PRs backported to 3.16 but not 3.22
>> :
>> is:pr label:"backport queued_ltr_backports" -label:"backport release-3_22"
>> 
>>  (same
>> search should also be done with label `backport release-3_16`)
>>
>> Shouldn't backporting to 3.16 always imply backporting to 3.22 ? Or am I
>> missing something ?
>>
>> Cheers !
>>
>> Olivier
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

2021-12-09 Thread Julien Cabieces 

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 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://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3A%22backport+queued_ltr_backports%22+-label%3A%22backport+release-3_22%22+merged%3A%3E2021-10-21
> since anything merged before 22/10/2021 is automatically in 3.22. Finally,
> there's no that much leftover PRs, so I think everybody is OK with your
> logic.
>
> Regards,
> Harrissou
>
> Le jeu. 9 déc. 2021 à 15:29, Olivier Dalang  a
> écrit :
>
>> 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 with the `backport queued_ltr_backports`
>> label, but without `backport release-3_22`.
>>
>> As far as I understand, this means it will be available in 3.24 (master)
>> and in 3.16 (after some quarantine), but not in 3.22. Still if I understand
>> correctly, 3.22 is our future LTR, meaning that LTR users will at some
>> point upgrade from 3.16 to 3.22. Does that mean that the bug they have seen
>> fixed in 3.16 will be reintroduced in 3.22 ?
>>
>> The following filter shows many other PRs backported to 3.16 but not 3.22 :
>> is:pr label:"backport queued_ltr_backports" -label:"backport release-3_22"
>> 
>>  (same
>> search should also be done with label `backport release-3_16`)
>>
>> Shouldn't backporting to 3.16 always imply backporting to 3.22 ? Or am I
>> missing something ?
>>
>> Cheers !
>>
>> Olivier
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

2021-12-09 Thread DelazJ 
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://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3A%22backport+queued_ltr_backports%22+-label%3A%22backport+release-3_22%22+merged%3A%3E2021-10-21
since anything merged before 22/10/2021 is automatically in 3.22. Finally,
there's no that much leftover PRs, so I think everybody is OK with your
logic.

Regards,
Harrissou

Le jeu. 9 déc. 2021 à 15:29, Olivier Dalang  a
écrit :

> 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 with the `backport queued_ltr_backports`
> label, but without `backport release-3_22`.
>
> As far as I understand, this means it will be available in 3.24 (master)
> and in 3.16 (after some quarantine), but not in 3.22. Still if I understand
> correctly, 3.22 is our future LTR, meaning that LTR users will at some
> point upgrade from 3.16 to 3.22. Does that mean that the bug they have seen
> fixed in 3.16 will be reintroduced in 3.22 ?
>
> The following filter shows many other PRs backported to 3.16 but not 3.22 :
> is:pr label:"backport queued_ltr_backports" -label:"backport release-3_22"
> 
>  (same
> search should also be done with label `backport release-3_16`)
>
> Shouldn't backporting to 3.16 always imply backporting to 3.22 ? Or am I
> missing something ?
>
> Cheers !
>
> Olivier
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

2021-12-09 Thread Olivier Dalang 
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 with the `backport queued_ltr_backports`
label, but without `backport release-3_22`.

As far as I understand, this means it will be available in 3.24 (master)
and in 3.16 (after some quarantine), but not in 3.22. Still if I understand
correctly, 3.22 is our future LTR, meaning that LTR users will at some
point upgrade from 3.16 to 3.22. Does that mean that the bug they have seen
fixed in 3.16 will be reintroduced in 3.22 ?

The following filter shows many other PRs backported to 3.16 but not 3.22 :
is:pr label:"backport queued_ltr_backports" -label:"backport release-3_22"

(same
search should also be done with label `backport release-3_16`)

Shouldn't backporting to 3.16 always imply backporting to 3.22 ? Or am I
missing something ?

Cheers !

Olivier
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer