-
Notifications
You must be signed in to change notification settings - Fork 47
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
☂️ Requirements for v0.4.0 release #350
Comments
lets startup policy as well as nice to have |
Sounds good, added. |
Which date is targetted for v0.4.0 release @danielvegamyhre ? |
Around March 1st. |
Added #75 to "nice to haves," since it is important but we are unlikely to have time to complete it by the next release. |
Added Graduating API to Beta to must-haves. #380 |
I would move #262 to the next release, and just focus on startup policy and v1 graduation in the 0.4 release. The reason is that I would like to make sure we have a conclusion on kubernetes/enhancements#4479 before we commit on the failure policy api, and I don't want to block the 0.4 release on that. |
This also leaves 0.5 with two sizable enhancements: failure policy and TTL with the exclusive placement API enhancement as a nice to have. |
Makes sense. In addition, #392 was an important change for fast restarts / failure recovery, which I think is important to included in a release ASAP. I will update the release requirements accordingly. |
True! lets add that to the list above and in the release notes. |
v0.4.0 has been released 🥳 |
Targeting release around March 1st, 2024.
Must haves
Nice to haves
The text was updated successfully, but these errors were encountered: