Cherry-picking policy

[David Redondo]

Am Samstag, 19. November 2022, 05:06:11 CET schrieb Ben Cooksley:
> Not sure how much of this is on our radar at the moment, but I do know that
> we were playing with a bot to do tagging of MRs at one point in time.
> 
> In terms of how this bot operates, how are people thinking it should work?

I quite like the way Qt does it, in the commit message footer you add 
for example 
"Pick to: 6.4 6.2"
and after the your change is merged to dev the bot creates MR for
the relevant branches.

Nate brought up label + milestone. Please correct me but you can only have one 
milestone I think. I guess it would need to work something like,
- if has "Cherry-pick" label and milestone LTS -> pick to LTS and stable
- if has "Cherry-pick" label and milestone stabel -> pick to stable

Do we have situations where we pick to more than stable and latest LTS?
The only thing that would come to my mind are security fixes after the
normal support period.

David