FINAL REMINDER: JavaFX 24 RDP1 starts tomorrow [was: Proposed schedule for JavaFX 24]

[Kevin Rushforth]

As a reminder, JavaFX 24 RDP1 starts tomorrow, January 16th. I will fork 
the 'jfx24' branch at 16:00 UTC.

-- Kevin


On 12/19/2024 4:05 PM, Kevin Rushforth wrote:
> As a reminder, Rampdown Phase 1 (RDP1) for JavaFX 24 starts on 
> Thursday, January 16, 2025 at 16:00 UTC (08:00 US/Pacific time). Given 
> the upcoming holidays, that's a little over 2 working weeks from now.
>
> During rampdown of JavaFX 24, the "master" branch of the jfx repo will 
> be open for JavaFX 25 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 9, or it is likely to 
> miss the window for this release, in which case it can be targeted for 
> JavaFX 25.
>
> We will follow the same process as in previous releases for getting 
> fixes into JavaFX 24 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 10/25/2024 11:34 AM, Kevin Rushforth wrote:
>> Here is the proposed schedule for JavaFX 24:
>>
>> RDP1: Jan 16, 2025 (aka “feature freeze”)
>> RDP2: Feb 6, 2025
>> Freeze: Feb 27, 2025
>> GA: Mar 18, 2025
>>
>> We plan to fork a jfx24 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.
>>
>> This schedule moves the RDP1 and RDP2 start dates back one week to 
>> better avoid running into the holidays like we usually do. This will 
>> give one extra week before RDP1 starts and one less week during RDP2 
>> (we historically have few fixes coming in during RDP2). We intend to 
>> use this as the new formula for computing the release schedule going 
>> forward.
>>
>> Please let Johan or me know if you have any questions.
>>
>> -- Kevin
>>
>