Add verification step to image release process (#24177)

(cherry picked from commit 5d5598e)
apache · Jun 30, 2022 · 4a11f46 · 4a11f46
1 parent b6aa680
commit 4a11f46
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
@@ -41,6 +41,7 @@
   - [Publish release to SVN](#publish-release-to-svn)
   - [Prepare PyPI "release" packages](#prepare-pypi-release-packages)
   - [Manually prepare production Docker Image](#manually-prepare-production-docker-image)
+  - [Verify production images](#verify-production-images)
   - [Publish documentation](#publish-documentation)
   - [Notify developers of release](#notify-developers-of-release)
   - [Add release data to Apache Committee Report Helper](#add-release-data-to-apache-committee-report-helper)
@@ -974,6 +975,18 @@ marked as "latest".
 In case we are releasing (which almost never happens so far) a critical bugfix release in one of
 the older branches, you should set the "skip" field to true.
 
+## Verify production images
+
+```shell script
+for PYTHON in 3.7 3.8 3.9 3.10
+do
+    docker pull apache/airflow:${VERSION}-python${PYTHON}
+    breeze verify-prod-image --image-name apache/airflow:${VERSION}-python${PYTHON}
+done
+docker pull apache/airflow:${VERSION}
+breeze verify-prod-image --image-name apache/airflow:${VERSION}
+```
+
 
 ## Publish documentation