Commit bots confused?
Kevin Rushforth
kevin.rushforth at oracle.com
Thu Jan 20 13:45:07 UTC 2022
No worries.
-- Kevin
On 1/20/2022 5:30 AM, Jeanette Winzenburg wrote:
>
> Thanks for the cleanup, Kevin - and sry for having created the mess ;)
>
> -- Jeanette
>
> Zitat von Kevin Rushforth <kevin.rushforth at oracle.com>:
>
>> Yes, this happened because the bug was still targeted to openjfx18. I
>> had meant to go through all of the issues still targeted to openjfx18
>> earlier this week, but then got busy with (too many) other things.
>>
>> I'll fix up the JBS records.
>>
>> Thanks.
>>
>> -- Kevin
>>
>>
>> On 1/20/2022 4:13 AM, Jeanette Winzenburg wrote:
>>>
>>> wondering what happened in https://github.com/openjdk/jfx/pull/684
>>> (fix for https://bugs.openjdk.java.net/browse/JDK-8187307)
>>>
>>> - requested integration (into master) after review approval
>>> - the bots did the usual thingies (commit, comment/close the issue
>>> in jbs)
>>> - the bots did some unusual thingies: creating a backport
>>> https://bugs.openjdk.java.net/browse/JDK-8280380 into jfx19 and
>>> commented/closed it as fixed immediately)
>>>
>>> verified that the commit (as of now) really is into master, not fx18
>>> - so the actual commits seem to be clean, it's just that weird
>>> auto-backport
>>>
>>> What might have confused them is that I didn't update the fix
>>> version of the issue (it's still fx18) after rampdown (being still
>>> in holiday mode ;)
>>>
>>> Anything I should do?
>>>
>>> -- Jeanette
>>>
>
>
>
More information about the openjfx-dev
mailing list