-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update release instructions in Python 3.10 #23702
Update release instructions in Python 3.10 #23702
Conversation
Codecov Report
@@ Coverage Diff @@
## master #23702 +/- ##
==========================================
- Coverage 73.34% 73.33% -0.01%
==========================================
Files 719 719
Lines 95794 95795 +1
==========================================
- Hits 70259 70251 -8
- Misses 24224 24233 +9
Partials 1311 1311
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@lostluck Do I need add Python 3.10 configuration anywhere in the |
I don't recall much in the way of Python version specific stuff appearing in the public open source release instructions. The scripts in the release directory would need to be checked probably? https://github.com/apache/beam/tree/master/release/src/main/scripts I know very very very little about our python infra and don't have any further pointers. |
@chamikaramj We added Python 3.10 to the next release. Do you know if I need to add anything else to beam/release dir so that Python 3.10 images are also get built during release? |
Assigning reviewers. If you would like to opt out of this review, comment R: @Abacn for label build. Available commands:
The PR bot will only process comments in the main thread (not review comments). |
R: @tvalentyn |
@AnandInguva you can check prior work or PR history for Python 3.9-related changes in those directories. |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.