Quarkus LTS support

[brice-laurencin]

With quarkus now supporting LTS versions, it feels like the extension should support those LTS versions for their support timeframe.

I clearly don't have any idea how it could move forward.
But I'd be happy to help if I can.

[hbelmiro]

We'll probably have multiple branches for each Quarkus version, like when we used to support Quarkus 3 and 2.

@ricardozanini @gastaldi thoughts?

[gastaldi]

@hbelmiro exactly. Some projects like https://github.com/quarkiverse/quarkus-artemis already do this

[ricardozanini]

@hbelmiro Yes, we have to branch from the main, roll back to LTS, and release a new version from this branch. We can have the same number but with a suffix like 1.2.3-lts.

@brice-laurencin I can create the branch. Can you work on a patch to follow the LTS in this new branch?

[brice-laurencin]

I can try, but I'm not sure I see all that must be done.
As you mentioned, I'd go from main and downgrade the quarkus version.

(And I might not be able to do this this week, but next week will be fine)

[jota-coelho]

With quarkus now supporting LTS versions, it feels like the extension should support those LTS versions for their support timeframe.

I clearly don't have any idea how it could move forward. But I'd be happy to help if I can.

Hello! I’d like to emphasize that I also need to migrate to the LTS version, so this update would be very helpful.

[ricardozanini]

@jota-coelho We are open to contributions.

I created the main-lts branch here: https://github.com/quarkiverse/quarkus-openapi-generator/tree/main-lts

Any PRs should be opened there, and the documentation should be updated to tell users about it. Once it's done, I can do the release.

@brice-laurencin once you open the PR, we can discuss more details if needed.

[brice-laurencin]

I think we need a branch per current LTS, mentioning the targeted version.
there are 2 LTS at the moment, and with 12 months of support, we could have up to 3 I suppose.

[ricardozanini]

@brice-laurencin I don't think we have the resources to keep up with the three branches. We can keep up with the latest LTS.

[brice-laurencin]

@ricardozanini technically, current main-lts references Quarkus 3.15.1, so it's already linking the latest LTS patch.

So I suppose everything is good?
Maybe we need to find a proper version pattern for those versions.

[ricardozanini]

We can support the older LTS instead. I think it will be more helpful for the community.

The version pattern could be 1.2.3-lts.

[hbelmiro]

We're about to support 3.16.

[ricardozanini]

@hbelmiro @brice-laurencin the idea is to support an old LTS, in this case Quarkus 3.8 LTS.

[hbelmiro]

My point is that we're close to supporting 3.16 in main. Once we do that, I'm assuming we would support 3.15 in main-lts.
That said, it's probably better just to wait for 3.16 than invest time to support 3.8 just for a few days.