This is an automated email from the ASF dual-hosted git repository. potiuk pushed a commit to branch update-release-airflow-pmc-check in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 9aeda18e62188043382fda3f9dba9e0f3d16232d Author: Jarek Potiuk <[email protected]> AuthorDate: Fri Feb 23 16:30:25 2024 +0100 Update README_RELEASE_AIRFLOW.md When PMC member builds packages locally with hatch, it will delete the tarball prepared before, so we need to reverse the sequence of commands. --- dev/README_RELEASE_AIRFLOW.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md index 5cecca59c0..c4ba5d0d3f 100644 --- a/dev/README_RELEASE_AIRFLOW.md +++ b/dev/README_RELEASE_AIRFLOW.md @@ -458,25 +458,28 @@ VERSION=X.Y.Zrc1 git checkout ${VERSION} export AIRFLOW_REPO_ROOT=$(pwd) rm -rf dist/* -breeze release-management prepare-airflow-tarball --version ${VERSION} breeze release-management prepare-airflow-package --package-format both +breeze release-management prepare-airflow-tarball --version ${VERSION} ``` -The last - build step - by default will use Dockerized build and building of Python client packages +The `prepare-airflow-package` by default will use Dockerized approach and building of the packages will be done in a docker container. However, if you have `hatch` installed locally you can use `--use-local-hatch` flag and it will build and use docker image that has `hatch` installed. ```bash breeze release-management prepare-airflow-package --package-format both --use-local-hatch +breeze release-management prepare-airflow-tarball --version ${VERSION} ``` -This is generally faster and requires less resources/network bandwidth. - -The tarball command should produce reproducible `-source.tar.gz` tarball of sources. +This is generally faster and requires less resources/network bandwidth. Note that you have to +do it before preparing the tarball as preparing packages cleans up dist folder from +apache-airflow artifacts as it uses hatch's `-c` build flag. The `prepare-airflow-package` command (no matter if docker or local hatch is used) should produce the reproducible `.whl`, `.tar.gz` packages in the dist folder. +The tarball command should produce reproducible `-source.tar.gz` tarball of sources. + Change to the directory where you have the packages from svn: ```shell script
