Release stabilization: Create backport issues immediately

[Mark Reinhold]

2023/12/13 11:41:00 -0500, weijun.wang at oracle.com:
> Or, we can still fix in the main line first and backport it. Only, let
> Skara do something different.
> 
> Suppose I keep the bug’s target to jdk22, currently the Skara bot is
> already able to notice it and shows a warning in the jdk23 PR. When
> the jdk23 PR is integrated, I wonder if the bot can:
> 
> 1. Change the JBS target to 23, where the fix is integrated
> 2. Create a backport for 22, which is the original target
> 
> If I remember correctly, its current behavior is to keep the original
> bug unchanged and create a “backport” for jdk23. If we believe that
> backport is always backward, this should be fixed anyway. If we
> believe a backport can be forward, then all is fine. The bug id used
> in the comment is still the non-backport one.

Arranging for a Skara bot to do something like this would require
non-trivial logic which we don’t have time to implement for JDK 22.
We’ll see how it goes this time with the tweaked process and consider
other possibilities later.

- Mark