[External] : Re: Proposed schedule for JavaFX 20
Kevin Rushforth
kevin.rushforth at oracle.com
Thu Dec 22 00:22:46 UTC 2022
As it turns out, it is the version of Xcode / macOS SDK that was used
the compile the JDK that matters, regardless of what we use to compile
JavaFX. That makes this is a more serious bug than initially thought.
I can reproduce it, and have sent a pull request for review:
https://github.com/openjdk/jfx/pull/981
-- Kevin
On 12/21/2022 5:42 AM, Kevin Rushforth wrote:
> As Johan said, the JavaFX releases are currently built with Xcode
> 12.4, so JDK-8296654 isn't directly relevant, unless it doesn't fully
> describe the problem. If you are seeing a crash on macOS 13 Ventura
> with the downloaded JavaFX SDK (built with Xcode 12.4), that would be
> a much more serious bug.
>
> Do you have a reproducible test case using a build from openjfx.io or
> jdk.java.net?
>
> I plan to do some macOS 13 testing in the next day or two, so can take
> a look if there is a reproducer.
>
> -- Kevin
>
>
> On 12/21/2022 12:26 AM, Johan Vos wrote:
>> There will be a new JavaFX 19 release with the security patches for
>> 2023Q1 (scheduled Jan 17).
>> Typically, those maintenance releases contain a few selected
>> backports from the head version.
>> However, in this case it seems unlikely to me as JDK-8296654 is not
>> resolved.
>> Once resolved, that is something that could go in the LTS backports
>> for 11 and 17.
>>
>> Looking into JDK-8296654, I'm not sure I understand the issue, as the
>> builds we do are with XCode 12.4 so that should not cause problems?
>>
>> - Johan
>>
>> On Wed, Dec 21, 2022 at 9:06 AM Glavo <zjx001202 at gmail.com> wrote:
>>
>> Will JavaFX 19 release an updated version?
>>
>> We have received a lot of feedback about program crashes on the
>> macOS. These crashes should be caused by JDK-8296654.
>> Because our program needs to be compatible with Java 11~16, it
>> cannot be updated to JavaFX 20.
>> It would be great if we could fix this problem in JavaFX 19.
>>
>> On Tue, Dec 20, 2022 at 4:10 AM Kevin Rushforth
>> <kevin.rushforth at oracle.com> wrote:
>>
>> As a reminder, Rampdown Phase 1 (RDP1) for JavaFX 20 starts
>> on January
>> 12, 2023 at 16:00 UTC (08:00 Pacific time). Given the
>> upcoming holidays,
>> that's a little over 2 working weeks from now.
>>
>> During rampdown of JavaFX 20, the "master" branch of the jfx
>> repo will
>> be open for JavaFX 21 fixes.
>>
>> Please allow sufficient time for any feature that needs a
>> CSR. New
>> features should be far enough along in the review process
>> that you can
>> finalize the CSR no later than Thursday, January 5, or it is
>> likely to
>> miss the window for this release, in which case it can be
>> targeted for
>> JavaFX 21.
>>
>> We will follow the same process as in previous releases for
>> getting
>> fixes into JavaFX 20 during rampdown. I'll send a message
>> with detailed
>> information when we fork, but candidates for fixing during
>> RDP1 are
>> P1-P3 bugs (as long as they are not risky) and test or doc
>> bugs of any
>> priority. Some small enhancements might be considered during
>> RDP1, but
>> they require explicit approval; the bar will be high for such
>> requests.
>>
>> -- Kevin
>>
>>
>> On 11/1/2022 1:59 PM, Kevin Rushforth wrote:
>> > Here is the proposed schedule for JavaFX 20.
>> >
>> > RDP1: Jan 12, 2023 (aka “feature freeze”)
>> > RDP2: Feb 2, 2023
>> > Freeze: March 2, 2023
>> > GA: March 21, 2023
>> > We plan to fork a jfx20 stabilization branch at RDP1.
>> >
>> > The start of RDP1, the start of RDP2, and the code freeze
>> will be
>> > 16:00 UTC on the respective dates.
>> >
>> > Please let Johan or me know if you have any questions.
>> >
>> > -- Kevin
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20221221/55ad8ed8/attachment.htm>
More information about the openjfx-dev
mailing list