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

☂️ Requirements for v0.4.0 release #350

Closed
5 of 7 tasks
danielvegamyhre opened this issue Dec 13, 2023 · 11 comments
Closed
5 of 7 tasks

☂️ Requirements for v0.4.0 release #350

danielvegamyhre opened this issue Dec 13, 2023 · 11 comments

Comments

@danielvegamyhre danielvegamyhre pinned this issue Dec 13, 2023
@ahg-g
Copy link
Contributor

ahg-g commented Dec 13, 2023

lets startup policy as well as nice to have

@danielvegamyhre
Copy link
Contributor Author

lets startup policy as well as nice to have

Sounds good, added.

@dejanzele
Copy link
Contributor

Which date is targetted for v0.4.0 release @danielvegamyhre ?

@danielvegamyhre
Copy link
Contributor Author

Around March 1st.

@danielvegamyhre
Copy link
Contributor Author

Added #75 to "nice to haves," since it is important but we are unlikely to have time to complete it by the next release.

@danielvegamyhre
Copy link
Contributor Author

Added Graduating API to Beta to must-haves. #380

@ahg-g
Copy link
Contributor

ahg-g commented Feb 9, 2024

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.

I think #344, #104 and #380 merits a release.

@ahg-g
Copy link
Contributor

ahg-g commented Feb 9, 2024

This also leaves 0.5 with two sizable enhancements: failure policy and TTL with the exclusive placement API enhancement as a nice to have.

@danielvegamyhre
Copy link
Contributor Author

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.

I think #344, #104 and #380 merits a release.

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.

@ahg-g
Copy link
Contributor

ahg-g commented Feb 9, 2024

True! lets add that to the list above and in the release notes.

@danielvegamyhre
Copy link
Contributor Author

v0.4.0 has been released 🥳

@danielvegamyhre danielvegamyhre unpinned this issue Feb 29, 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

No branches or pull requests

3 participants