-
Notifications
You must be signed in to change notification settings - Fork 510
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 schedule for this project? #832
Comments
We've noticed a few outdated dependencies which could do with being updated in this project, and unsure what exactly the approach is to go control plane planning. |
cc @alecholmez ( I see that you are maintainer for the repo and made the latest releases) |
We've been going back and forth on some release cycle stuff, once the multi-module release plan lands that will become a lot smoother. In the meantime I can cut another patch release that pulls in the latest envoy configurations. |
Anything I can do to help? |
Checking this out would help! #714 I've got some catching up to do on that but hopefully can get it in soon |
I just pushed 0.12.0, but doesn't tackle the release schedule question yet. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
Is there any doc about when to kick off a release?
It seems that this project doesn't follow the same release schedule as Envoy. What if people want to use a new field added in the latest Envoy release, but this project hasn't provided a match release yet?
Thanks for your reply.
The text was updated successfully, but these errors were encountered: