8000 [Auto Release] Update istio.Version by sebastienvas · Pull Request #624 · istio/istio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[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

Merged
merged 1 commit into from
Aug 31, 2017
Merged

Conversation

sebastienvas
Copy link
Contributor

Update istio.Version

@istio-merge-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
We suggest the following additional approver: ldemailly

Assign the PR to them by writing /assign @ldemailly in a comment when ready.

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 /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@sebastienvas
Copy link
Contributor Author

@linsun I am not sure I understand this failure from IBM tests. Did you guys updated bazel to be 0.5.3 ?

@gyliu513
Copy link
Member

@sebastienvas is there a CHANGELOG for this?

@sebastienvas
Copy link
Contributor Author

@yutongz do you have the release note generation working ? Otherwise we might have to ask for the team to come up with one.

@sebastienvas
Copy link
Contributor Author

@gyliu513 are you volunteering to gather release note from people ?

@gyliu513
Copy link
Member

@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 istio/features, and draft the release note there, everyone can add his own projects there, then we can publish it at https://github.com/istio/istio/CHANGELOG , comments?

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.

@sebastienvas
Copy link
Contributor Author

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 ?

@sebastienvas
Copy link
Contributor Author

/retest

@sebastienvas
Copy link
Contributor Author

/test all

1 similar comment
@sebastienvas
Copy link
Contributor Author

/test all

@sebastienvas sebastienvas merged commit 6077ca3 into master Aug 31, 2017
@istio-testing
Copy link
Collaborator

@sebastienvas: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
prow/e2e-suite-rbac-auth.sh b74d863 link /test e2e-suite-rbac-auth
prow/e2e-suite-no_rbac-auth.sh b74d863 link /test e2e-suite-no_rbac-auth

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.

@gyliu513
Copy link
Member

@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.

@gyliu513
Copy link
Member
gyliu513 commented Sep 1, 2017

@sebastienvas when we will have official 0.2 release? I was planning to update the istio chart here helm/charts#1909

@sebastienvas
Copy link
Contributor Author

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.

@ldemailly
Copy link
Member

the release notes have been hastily put together and 0.2.1 isn't an official release yet.
hopefully we will have a real release with more complete notes in a couple of weeks

this being said you can get all the changes using links like:
istio/old_pilot_repo@0.1.6...0.2.1
istio/old_mixer_repo@0.1.6...0.2.1
0.1.6...0.2.1
etc

@gyliu513 gyliu513 deleted the Istio_Release_0.2.1 branch September 7, 2017 04:53
@gyliu513
Copy link
Member
gyliu513 commented Sep 7, 2017

@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.

rshriram pushed a commit that referenced this pull request Oct 30, 2017
vbatts pushed a commit to vbatts/istio that referenced this pull request Oct 31, 2017
mandarjog pushed a commit that referenced this pull request Nov 2, 2017
0x01001011 pushed a commit to thedemodrive/istio that referenced this pull request Jul 16, 2020
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 this pull request may close these issues.

6 participants
0