Code changes required after JDK-8291473

[Maurizio Cimadamore]

On 04/08/2022 19:17, Filip Krakowski wrote:
> Hi Maurizio,
>
>> When JDK N is GA'ed, we do two things:
>>
>> * we "freeze" the contents of the "main" branch into a branch called 
>> jdkN-1
>> * we move "next" into "main" (so we'll start generating binary 
>> snapshot that refer to the latest GA'ed JDK release).
> if I understand it correctly, the "next" branch would be the branch 
> for the next JDK waiting to be GA'ed and "main" would hold the 
> currently GA'ed JDK (generating binary snapshots)? If yes, wouldn't 
> the same problem reappear once development for JDK 21 starts? "next" 
> would be pointing to JDK 20 (the next version to be GA'ed) and there 
> would be no place for JDK 21.

Let's say the last GA'ed release is 26.

Then, the "main" branch will point at jextract for 26.

There will also be branches for 25, 24, 23, ....

And the "next" branch will at an experimental version of jextract which 
works with 27.

What you say is true, though - there is a lag between when JDK N + 1 is 
created and worked upon and when JDK N is GA'ed. In this temporal 
interval (which is where we are now, and lasts for about 3 months).

Another option, which is perhaps simpler, is just to have "main" and 
"jdkN" branches.

When JDK N is created, we also create corresponding branch on jextract.

The "main" branch is only updated when a new JDK N is GA'ed (by copying 
contents from the already existing JDK N branch).

Maurizio

>
> Best regards,
> Filip
>
>