Add more detailed instructions on how to check pre-release candidates #32948
Conversation
This file contains 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
We ask our contributors to test pre-release candidates for Airflow and providers, but not everyone knows that Breeze allows to easily mix&match versions of airflow and providers that can be installed when running `breeze shell` or `breeze start-airflow` - which helps to test release candidates manually very, very quickly. This change adds more detailed explanation and examples showing how it can be done, and links to those instruction from our release announcements and release documentation.
potiuk
requested review from
ephraimbuddy,
hussein-awala,
eladkal and
jedcunningham
69 tasks
pankajkoti
reviewed
Jul 30, 2023
potiuk
commented
Jul 30, 2023
Co-authored-by: Pankaj Koti <[email protected]>
Co-authored-by: Pankaj Koti <[email protected]>
pankajkoti
approved these changes
Jul 30, 2023
potiuk
force-pushed
the
add-description-on-how-to-test-release-candidates
branch
from
d0e9da6
to
3963955
Compare
Adaverse
reviewed
Jul 30, 2023
Co-authored-by: Akash Sharma <[email protected]>
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jul 30, 2023
After merging apache#32948 I realised the links were pointing to a sub-section and the name was not encouraging. This PR fixes it as a very small follow-up.
potiuk
added a commit
that referenced
this pull request
Jul 30, 2023
After merging #32948 I realised the links were pointing to a sub-section and the name was not encouraging. This PR fixes it as a very small follow-up.
pankajkoti
added a commit
to astronomer/airflow
that referenced
this pull request
Aug 7, 2023
With the header change in PR apache#32948, the link to Verify by contributors in the Status of providers testing issue in broken. Correct the same by pointing it to the right header.
pierrejeambrun
pushed a commit
that referenced
this pull request
Aug 7, 2023
With the header change in PR #32948, the link to Verify by contributors in the Status of providers testing issue in broken. Correct the same by pointing it to the right header.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We ask our contributors to test pre-release candidates for Airflow and providers, but not everyone knows that Breeze allows to easily mix&match versions of airflow and providers that can be installed when running
breeze shellorbreeze start-airflow- which helps to test release candidates manually very, very quickly.This change adds more detailed explanation and examples showing how it can be done, and links to those instruction from our release announcements and release documentation.
^ 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.