<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
That would just cause more confusion. None of our tools or queries
are set up to work well in the presence of multiple fix versions.<br>
<br>
-- Kevin<br>
<br>
<br>
<div class="moz-cite-prefix">On 12/13/2023 5:52 PM,
<a class="moz-txt-link-abbreviated" href="mailto:dean.long@oracle.com">dean.long@oracle.com</a> wrote:<br>
</div>
<blockquote type="cite" cite="mid:f1ea66a2-ff0f-4ed1-be6a-f1f87f828427@oracle.com">
<p>On 12/13/23 6:18 AM, Mark Reinhold wrote:</p>
<blockquote type="cite" cite="mid:20231213091848.160388671@eggemoggin.niobe.net">
<pre> To fix a bug in the stabilization release, first target that bug to
the main-line release and **immediately create a backport of the bug
and target the backport to the stabilization release.** Then create
a PR to integrate your fix into the main-line release. After you
have obtained any necessary approvals, backport the main-line PR to
the stabilization repository via the Skara `/backport` command.</pre>
</blockquote>
<p><br>
</p>
<p>JIRA seems to allow multiple Fix Versions, so I'm wondering if
the fix versions were set to main-line <i>and</i> 22, would
Skara PR logic and candidate-bug queries do the right thing, or
would it just cause more confusion?</p>
<p>dl<br>
</p>
</blockquote>
<br>
</body>
</html>