Hello!
I had started to prepare F43 change of java-25-openjdk as system jdk in f43, but during writeup, I found the dates do not match:
You may see, that between July security update, and fedora branching is less then month of time during main summer time. During that time, upstream jdk must fork (it will), java-latest-openjdk must update to jdk25, java-25-openjdk package must be created, and built in koji. Then Maven and ant bootstrap must be done. In case of jdk25 the bigger mass rebuild may not be necessary. I will most likely run it, but if it fails, the straightforward fix is to revert back to jdk21 as ant, maven and friends are already less bound by any "system jdk". They expect that any jdk may provide "java" This fix is in javapackages-tools since 9.2024, however docs are being updated only now.
The dates, as they are now, are manageable. Having branching delayed by week, or better by two, will make the transition much less stressful, and much more sure and prone against missing human or some errors
How many (Fedora) packages are we talking about? Although the branching will occur on 12/08, the "change checkpoint: 100% Code Complete Deadline" will not occur until the 26/08. If we are talking about a small number of packages, would it be possible to eventually do it in rawhide and then backport it to F43?
Maven / Ant ecosystem accounts for some 120 packages.
The system JDK mass rebuild is usually around 500 packages. I know the deadline is alter, but we did the mistake of doing system jdk after branching only once, and I really do not want to repeat that error.
As for the 500affected packages - this system jdk mass rbeuild, may no longer be necessary. This is something I had not yet still fully thought through,
The maven/ant botstrap is what metters more. that must be done before branching.
The backup plan is not to delay the feature, but to merge it earlier, with very early preview candidate, and thus risking false negatives in builds.
I don't think we want to delay branching. Any changes to the release schedule cause cascading effects. I think that introducing early preview candidates is a better solution. There might be some bugs caused by the compiler or the java runtime, but that'll actually allow them to be resolved earlier.
I'll close this. Please build earlier with the preview candidate. This is what we do in many other cases. If you disagree and think this should be discussed more, please reopen.
Metadata Update from @zbyszek: - Issue close_status updated to: Rejected - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.