-
Notifications
You must be signed in to change notification settings - Fork 8k
[Auto Release] Update istio.Version #624
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
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@linsun I am not sure I understand this failure from IBM tests. Did you guys updated bazel to be 0.5.3 ? |
@sebastienvas is there a CHANGELOG for this? |
@yutongz do you have the release note generation working ? Otherwise we might have to ask for the team to come up with one. |
@gyliu513 are you volunteering to gather release note from people ? |
@sebastienvas I'd love to be the volunteer, but I found that the istio have no CHANGELOG since day one... Like Kubenretes, we should have the CHANGELOG for each release. For Kubenretes, it has a repo https://github.com/kubernetes/features which will define tasks for each release cycle and release note, perhaps we can follow that way? How about create a new repo named as BTW: This is kubernetes draft 1.8 release note: https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md , we can follow this. |
Thanks for volunteering. I am just noticing that k8s started this process for 1.2. We need a formal process before 1.0, for sure but I believe that using github pages for release, and generated (or manual) release notes would be sufficient for now. Do you know who put this process in place for k8s, such that we understand the requirement behind it and why it was done that way ? |
/retest |
/test all |
1 similar comment
/test all |
@sebastienvas: The following tests failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@sebastienvas please checkout here for detail kubernetes/community#484 Congrats to 0.2.1, but for the release here https://github.com/istio/istio/releases/tag/0.2.1 , I found that we only list features, but did not mention who introduced this and what is the issue number of this feature, it would be great if we also have such info. |
@sebastienvas when we will have official 0.2 release? I was planning to update the istio chart here helm/charts#1909 |
I don't think we know that yet. Not all the features are in, and we still need to run some stabilization phase. Maybe @sakshigoel12 can give you an approximation. |
the release notes have been hastily put together and 0.2.1 isn't an official release yet. this being said you can get all the changes using links like: |
@sebastienvas @sakshigoel12 @ldemailly thanks all for the comments here, one comment for release, I do hope that we can release agilely with some significant features, such as the transparent injection here istio/old_pilot_repo#335 , this will impact some other projects, such as helm charts helm/charts#1909 etc, I do hope that we can have a official release which can support this feature soon. |
Former-commit-id: 6077ca3
Update istio.Version