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
Fix TF 2.7 release notes #52990
Fix TF 2.7 release notes #52990
Conversation
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@googlebot I consent. I already have the CLA signed. I'm not sure why this was asked. |
CLA bot is confused when doing cherrypicks. There's a caveat here, we'll add a new commit on the branch after the release, but probably we can handle this the same as #52971 |
3a5aa42
to
cdea395
Compare
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
I didn't cherry-pick anything here.
Can you confirm that, I need to do this commit on top of master and not on the release branch? I updated this PR to do this. I changed the RELEASE.md files instead of README.md. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
So we need one PR against the r2.7 branch and one against master. This way we ensure that the relnotes on the branch are always a subset of what's on master, each section matching. After the r2.7 branch PR lands I will update the GitHub release notes to match. |
cdea395
to
3a5aa42
Compare
Ok. So I updated this PR to be as at the start to modify only the 2.7 branch. @googlebot I consent. |
Looks good |
Fix #52670. The changes is in TF2.7 and not 2.6.
@mihaimaruseac