You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2023/11/13 22:06:24 UTC
(airflow-client-python) branch add-instructions-for-pmc-members created (now 42eb692)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch add-instructions-for-pmc-members
in repository https://gitbox.apache.org/repos/asf/airflow-client-python.git
at 42eb692 Add instructions on how to verify sources for PMC members
This branch includes the following new commits:
new 42eb692 Add instructions on how to verify sources for PMC members
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(airflow-client-python) 01/01: Add instructions on how to verify sources for PMC members
Posted by po...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch add-instructions-for-pmc-members
in repository https://gitbox.apache.org/repos/asf/airflow-client-python.git
commit 42eb6924efabafe8bcd3fc7944f97d7d6de99203
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Mon Nov 13 23:05:53 2023 +0100
Add instructions on how to verify sources for PMC members
---
dev/README_RELEASE_CLIENT.md | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/dev/README_RELEASE_CLIENT.md b/dev/README_RELEASE_CLIENT.md
index 6ef9c93..b97cb2f 100644
--- a/dev/README_RELEASE_CLIENT.md
+++ b/dev/README_RELEASE_CLIENT.md
@@ -283,6 +283,20 @@ See Airflow process documented [here](https://github.com/apache/airflow/blob/mas
## Signature check
See Airflow process documented [here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#signature-check).
+## Sources check
+
+The code of the Python Client is generated using Open API generator and the generated code is committed to
+the repository, therefore the Source code check should consist of two steps:
+
+1. Checkout the release tag of the "airflow-client-python"
+2. Follow the [Release process](#release-process) above and generate client's code above
+3. Run ``git diff`` to see the differences - review them. Generally the code generated should only contain
+ small differences regarding authentication.
+4. git reset --hard <RELEASE_TAG>
+
+Compare the sources with the packaged sources following the process describd in Airflow:
+[here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#signature-check).
+
# Verify release candidates by Contributors
This can be done (and we encourage to) by any of the Contributors. In fact, it's best if the
actual users of Airflow Client test it in their own staging/test installations. Each release candidate
@@ -442,4 +456,4 @@ Send the same email to announce@apache.org, except change the opening line to De
## Add release data to Apache Committee Report Helper
-Add the release data (version and date) at: https://reporter.apache.org/addrelease.html?airflow
\ No newline at end of file
+Add the release data (version and date) at: https://reporter.apache.org/addrelease.html?airflow