Remove pypitest from the release process#36466
Merged
hussein-awala merged 1 commit intoapache:mainfrom Dec 28, 2023
Merged
Conversation
It does not bring much value and we are skipping it anyway as we have no way to manage organisations in `pypitest`. It's also largely deprecated and abandoned by PyPi maintainers. Removing it from the process so that new release managers are not confused by it.
Lee-W
approved these changes
Dec 28, 2023
Taragolis
approved these changes
Dec 28, 2023
hussein-awala
approved these changes
Dec 28, 2023
potiuk
added a commit
that referenced
this pull request
Dec 30, 2023
(cherry picked from commit c16b421)
68 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It does not bring much value and we are skipping it anyway as we have no way to manage organisations in
pypitest. It's also largely deprecated and abandoned by PyPi maintainers.Removing it from the process so that new release managers are not confused by it.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.