-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Release v3.0 with Quarkus 3 support #294
Comments
I think we should upgrade to JHipster 8 before we release v3.0. |
Aside dependencies and docker images/keycloak realm, do you see any specific feature that would be helpful to wait for? I have few more Quarkus specific feature updates in mind and will create tickets for same (though not very sure if I can spend time on those :) ) |
@vishal423 No. Upgrading to JHipster 8 and Quarkus 3 is enough to warrant a release. I think that's a good foundation, and we can add new features in minor releases. |
Please advise if you want me to file a separate feature request, but would like to request |
I think you should open a new feature request. |
I will start working on the v8 migration. |
LGTM! What do you think @vishal423? |
Overall looks good to me. I am traveling and wouldn't be able to take
closer look before last week of November.
…On Thu, 9 Nov, 2023, 4:56 am Matt Raible, ***@***.***> wrote:
LGTM! What do you think @vishal423 <https://github.com/vishal423>?
—
Reply to this email directly, view it on GitHub
<#294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2BV4LLNBM6MHY2N4MFVB3YDQIKZAVCNFSM6AAAAAA4UNHA66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSHA4DSMRYG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mshima approved |
Please edit this description and add tasks as appropriate.
The text was updated successfully, but these errors were encountered: