Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to Red Hat Build of Quarkus #79

Open
yrodiere opened this issue Dec 12, 2023 · 2 comments
Open

Migrate to Red Hat Build of Quarkus #79

yrodiere opened this issue Dec 12, 2023 · 2 comments

Comments

@yrodiere
Copy link
Member

yrodiere commented Dec 12, 2023

See https://access.redhat.com/documentation/en-us/red_hat_build_of_quarkus/quarkus-3.2/guide/8c2d0754-31e2-4d6d-9d5f-9ade55c3b30d for instructions for 3.2; it'll probably be similar for later versions.

We'll want to wait for RHBQ 3.7/3.8 to be out, because migrating now would mean downgrading from Quarkus 3.6 to 3.2, and that would mean some annoying changes in tests.

@marko-bekhta
Copy link
Collaborator

Now we'd have to wait for a 3.10+ as we are using the standalone mapper.
And thinking more about this particular one, do we really want to stay on a RHBQ version or stay on the latest available and be able to test any new features we add to Search on a real application?

@yrodiere
Copy link
Member Author

yrodiere commented Jul 29, 2024

do we really want to stay on a RHBQ version or stay on the latest available and be able to test any new features we add to Search on a real application?

Depends who "we" is. Personally, I'd vote for always using the latest. But I understand the core Quarkus team may want to focus testing on LTS.

I think we'll probably end up doing this only if some compelling arguments show up, or if someone else who thinks it's a good idea actually puts in the work to maintain this project.

So... let's put this on ice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants