HEADS-UP: JBS fix versions changing on Feb 28 from "openjfxNN" to "jfxNN"

[Kevin Rushforth]

This transition is complete. Let me know if there are any questions or 
issues.

-- Kevin

On 2/27/2023 5:50 AM, Kevin Rushforth wrote:
> As a reminder, I plan to make this JBS version change live at 
> https://bugs.openjdk.org/ on Tuesday, Feb 28th (tomorrow) at 16:00 UTC.
>
> -- Kevin
>
>
> On 2/15/2023 4:43 AM, Kevin Rushforth wrote:
>> If you run JBS queries to find or filter out JavaFX bugs, please read 
>> this. Otherwise, you can ignore this.
>>
>> The unbundled JavaFX versions (11 and later) in JBS follow the 
>> pattern "openjfxNN[.0.MM]". We intend to globally rename all of the 
>> JavaFX fix versions in JBS from "openjfxNN[.0.MM]" to "jfxNN[.0.MM]". 
>> You will need to update any JBS queries that either reference an 
>> explicit "openjfxNN" version or use "openjfx" as part of a regex to 
>> use "jfx" instead.
>>
>> For example:
>>
>> openjfx21 --> jfx21
>> openjfx20 --> jfx20
>> openjfx17.0.7 --> jfx17.0.7
>> openjfx11.0.19 --> jfx11.0.19
>> ...
>>
>> The planned cut-over date is Tuesday, Feb 28. As part of this, I 
>> filed JDK-8302470 [1] to update the JBS version field in 
>> .jcheck/conf. I will prepare PRs for all active code lines and 
>> integrate them immediately after the JBS version renaming is done.
>>
>> NOTE: this change only affects JBS fix versions. There is no change 
>> or impact at all to those developing or using JavaFX.
>>
>> -- Kevin
>>
>> [1] https://bugs.openjdk.org/browse/JDK-8302470
>>
>