Update description of release process to include options for next RCs#36506
Merged
potiuk merged 2 commits intoapache:mainfrom Dec 31, 2023
Merged
Update description of release process to include options for next RCs#36506potiuk merged 2 commits intoapache:mainfrom
potiuk merged 2 commits intoapache:mainfrom
Conversation
potiuk
requested review from
amoghrajesh,
eladkal,
hussein-awala and
o-nikolas
and removed request for
amoghrajesh,
kaxil,
o-nikolas and
pierrejeambrun
potiuk
force-pushed
the
update-release-summary-message
branch
2 times, most recently
from
623e96a to
005d953
Compare
potiuk
force-pushed
the
update-release-summary-message
branch
3 times, most recently
from
634ab03 to
92869e7
Compare
Member
Author
|
Also improved notification message to always include list of packages as "appendix" - previously we had some conditional list there - in order to keep the message short for long list of packages, but I think it makes sense to add the links as appendix instead - most of our users will want to see the direct links to PyPI. |
Often we excluded individual providers from release and we have two options how to handle them - either release them on their own with an accelerated vote, or include the providers in the next wave of providers. This PR improves description of our process and email template to explain it better and guide the release manager on what to do. Also improved notification message
potiuk
force-pushed
the
update-release-summary-message
branch
from
92869e7 to
10304fd
Compare
hussein-awala
approved these changes
Dec 31, 2023
Co-authored-by: Hussein Awala <hussein@awala.fr>
potiuk
added a commit
that referenced
this pull request
Jan 13, 2024
…#36506) * Update description of release process to include options for next RCs Often we excluded individual providers from release and we have two options how to handle them - either release them on their own with an accelerated vote, or include the providers in the next wave of providers. This PR improves description of our process and email template to explain it better and guide the release manager on what to do. Also improved notification message Co-authored-by: Hussein Awala <hussein@awala.fr> --------- Co-authored-by: Hussein Awala <hussein@awala.fr> (cherry picked from commit 52a16bf)
potiuk
added
the
changelog:skip
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 15, 2024
…#36506) * Update description of release process to include options for next RCs Often we excluded individual providers from release and we have two options how to handle them - either release them on their own with an accelerated vote, or include the providers in the next wave of providers. This PR improves description of our process and email template to explain it better and guide the release manager on what to do. Also improved notification message Co-authored-by: Hussein Awala <hussein@awala.fr> --------- Co-authored-by: Hussein Awala <hussein@awala.fr> (cherry picked from commit 52a16bf)
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
2 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.
Often we excluded individual providers from release and we have two options how to handle them - either release them on their own with an accelerated vote, or include the providers in the next wave of providers.
This PR improves description of our process and email template to explain it better and guide the release manager on what to do.
Also improved notification message
^ 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.