Add Guide to release Apache Airflow Upgrade Check#14690
Conversation
kaxil
force-pushed
the
add-upgrade-check-release-guide
branch
2 times, most recently
from
2f82e42 to
6aed21d
Compare
There was a problem hiding this comment.
Oh, I should release this to pypi!
There was a problem hiding this comment.
I don't think you need to run egg_info command manually, sdist will do that automatically I thought
There was a problem hiding this comment.
Yeah, egg_info is only needed when preparing the pypi snapshot so that we can pass --tag-build option, but we shouldn't need it here.
There was a problem hiding this comment.
| ```shell | |
| ```shell script |
There was a problem hiding this comment.
Let's add .rat-excludes too
| airflow/upgrade NOTICE LICENSE licenses/ | |
| airflow/upgrade NOTICE LICENSE licenses/ .rat-excludes |
There was a problem hiding this comment.
| ```shell | |
| ```shell script |
There was a problem hiding this comment.
(Future enhancement: We should really work out how to just release the artifacts we votes on, rather than build new ones)
There was a problem hiding this comment.
I believe we should simply take the packages we vote on from SVN after we renamed them. I see no reason why it should not work. It should work the same for airflow, upgrade check and providers.
This commit adds guide to release Apache Airflow Upgrade Check
kaxil
force-pushed
the
add-upgrade-check-release-guide
branch
from
6aed21d to
230582f
Compare
github-actions
bot
added
the
okay to merge
|
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest master or amend the last commit of the PR, and push it with --force-with-lease. |
| Subject: | ||
|
|
||
| ``` | ||
| [VOTE] Release apache-airflow-upgrade-check 1.3.0 from 1.3.0rc1 |
There was a problem hiding this comment.
Maybe good to your VERSION from variable? I am not sure if we ever do it again but replacing the version is kinda easy to miss .
| <https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#verify-release-candidates-by-contributors>, | ||
| but again, this time it is a little bit different. | ||
|
|
||
| To actually use this command you will need apache-airflow 1.10.14 |
There was a problem hiding this comment.
| To actually use this command you will need apache-airflow 1.10.14 | |
| To actually use this command you will need apache-airflow 1.10.15 |
There was a problem hiding this comment.
I believe we should simply take the packages we vote on from SVN after we renamed them. I see no reason why it should not work. It should work the same for airflow, upgrade check and providers.
3 participants
This commit adds guide to release Apache Airflow Upgrade Check
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.