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

Question Regarding CRaC Feature Status on Micronaut Launch – Still in Preview? #2661

Closed
rjaros87 opened this issue Sep 23, 2024 · 2 comments · Fixed by #2660
Closed

Question Regarding CRaC Feature Status on Micronaut Launch – Still in Preview? #2661

rjaros87 opened this issue Sep 23, 2024 · 2 comments · Fixed by #2660

Comments

@rjaros87
Copy link

Issue description

I noticed that when using the Micronaut Launch page, the CRaC (Coordinated Restore at Checkpoint) feature is still marked as Preview. Given that Azul's CRaC project has released production-ready builds and several frameworks have integrated CRaC for production use, I wanted to clarify the current status of CRaC in Micronaut.

  1. Is the Preview label on the launch page accurate, and is CRaC still not considered production-ready within the Micronaut framework?
  2. If CRaC support is still in development or pending further testing, could you provide details on what remains to be done before it reaches production status?
  3. Alternatively, if this is an oversight, could the label on the feature list be updated to reflect its current status?
    Thank you for your time, and I appreciate all the great work being done with Micronaut!
@rjaros87
Copy link
Author

Is this project still supported / alive? :)
@sdelamo maybe you know something about this?
Thanks in advance.

@sdelamo
Copy link
Contributor

sdelamo commented Nov 20, 2024

I will remove the preview flag. thanks for the heads up.

@sdelamo sdelamo transferred this issue from micronaut-projects/micronaut-crac Nov 20, 2024
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

Successfully merging a pull request may close this issue.

2 participants