jextract standalone repository

[Maurizio Cimadamore]

On 25/03/2022 11:01, Sebastian Stenzel wrote:
>> On 25. Mar 2022, at 11:38, Maurizio Cimadamore <maurizio.cimadamore at oracle.com> wrote:
>>
>>
>> On 25/03/2022 09:36, Rémy Maucherat wrote:
>>> This is excellent.
>>>
>>> Ideally, there should also be a branch in the repository targeting
>>> Java 17 (since it's LTS) and another one for preview changes (there is
>>> no jextract for foreign-preview).
>> The idea is that, moving forward, we will create a branch to "freeze" the code before we move the jextract code to support a new release.
>>
>> So, now master has the Java 18 code; when we'll ship 19, we'll create a 18 branch with the code that is now in master, and apply the 19 changes onto the master.
>>
>> That way master always means "current Java release".
>>
>> We might try adding a branch for 17 - but we might not be able to offer binaries for it (when binaries become available).
>>
>> Maurizio
>>
> Since this is a new repo and therefore you can't argue that 3rd parties depend on its established structure, may I suggest to stick to 2020s standards and rename master to main? :)

That is a possibility - although I don't know how that will play with 
out internal infra to generate binary snapshot (which might depend on 
established structure after all).

Maurizio