Skip to content

1.3.3 release notes#5122

Merged
istio-testing merged 5 commits intoistio:masterfrom
brian-avery:1.3.3-release-notes
Oct 14, 2019
Merged

1.3.3 release notes#5122
istio-testing merged 5 commits intoistio:masterfrom
brian-avery:1.3.3-release-notes

Conversation

@brian-avery
Copy link
Member

Please provide a description for what this PR is for.

And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ x] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@brian-avery brian-avery requested a review from a team as a code owner October 10, 2019 20:35
@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Oct 10, 2019
@istio-testing istio-testing added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 10, 2019
@brian-avery brian-avery requested review from a team, rlenglet and sdake October 10, 2019 20:37
@rlenglet rlenglet mentioned this pull request Oct 10, 2019
24 tasks
@rlenglet
Copy link
Contributor

Can you also update the full_version number in data/args.yaml like in #5070? I think it's better to do it all in a single PR.

@brian-avery
Copy link
Member Author

Sure. This is the PR to master though, which is already updated to 1.4. Will add that in the cherry pick branch.

@rlenglet
Copy link
Contributor

Sure. This is the PR to master though, which is already updated to 1.4. Will add that in the cherry pick branch.

Sure, you're right.

Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. and removed cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. labels Oct 10, 2019
@rlenglet rlenglet added cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. and removed cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. labels Oct 10, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. and removed cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. labels Oct 11, 2019
@rlenglet rlenglet removed the cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. label Oct 11, 2019
@rlenglet rlenglet added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Oct 11, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@brian-avery
Copy link
Member Author

/test lint_istio.io

@brian-avery brian-avery added the do-not-merge Block automatic merging of a PR. label Oct 11, 2019
@brian-avery
Copy link
Member Author

brian-avery commented Oct 11, 2019

Added do not merge label in this PR so we can merge it on release.

@geeknoid
Copy link
Contributor

@brian-avery Note that this will need to be merged into release-1.3 in order to be published to istio.io. And note that as part o merging the PR to that branch, you also need to update the full_version field in data/args.yaml.

@brian-avery
Copy link
Member Author

@geeknoid Understood. Thanks. Added the cherry-pick to 1.3 label already, so as soon as this merges, that PR will open. Master already has data/args updated for 1.4 so I'm going to update the cherry-pick branch with the change.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. and removed cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. labels Oct 11, 2019
@brian-avery
Copy link
Member Author

@googlebot I fixed it

@rlenglet rlenglet added cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. and removed cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. labels Oct 11, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

Copy link
Contributor

@kyessenov kyessenov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nothing from policy&telemetry

@rlenglet
Copy link
Contributor

The tests on 1.3.3 look good. We can go ahead with the release.

@geeknoid geeknoid removed do-not-merge Block automatic merging of a PR. cherrypick/release-1.3 labels Oct 14, 2019
@istio-testing istio-testing merged commit 955b93a into istio:master Oct 14, 2019
rlenglet pushed a commit that referenced this pull request Oct 14, 2019
* 1.3.3 release notes

* 1.3.3 release notes

* Apply suggestions from code review

Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>

* Added note regarding Envoy crash
This was referenced Oct 14, 2019
rlenglet pushed a commit that referenced this pull request Oct 14, 2019
* 1.3.3 release notes

* 1.3.3 release notes

* Apply suggestions from code review

Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>

* Added note regarding Envoy crash
istio-testing pushed a commit that referenced this pull request Oct 14, 2019
* 1.3.3 release notes (#5122)

* 1.3.3 release notes

* 1.3.3 release notes

* Apply suggestions from code review

Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>

* Added note regarding Envoy crash

* Update full_version to 1.3.3
charili pushed a commit to charili/istio.io that referenced this pull request Nov 10, 2019
* 1.3.3 release notes (istio#5122)

* 1.3.3 release notes

* 1.3.3 release notes

* Apply suggestions from code review

Co-Authored-By: Romain Lenglet <romain.lenglet@berabera.info>

* Added note regarding Envoy crash

* Update full_version to 1.3.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants