[airflow] 01/11: Add verification step to image release process (#24177)

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ephraimanierobi pushed a commit to branch v2-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit 4a11f46ca204713e984c8338a62f8c4a99e9b67f
Author: Jarek Potiuk <ja...@polidea.com>
AuthorDate: Sat Jun 4 23:09:27 2022 +0200

    Add verification step to image release process (#24177)
    
    (cherry picked from commit 5d5598eca6ae4513e2decd851d32db992b6a02ec)
---
 dev/README_RELEASE_AIRFLOW.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
index 98f3062134..7e2cc8da83 100644
--- 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