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

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-client-python.git


The following commit(s) were added to refs/heads/main by this push:
     new 9dea92f  Add instructions on how to verify sources for PMC members 
(#101)
9dea92f is described below

commit 9dea92f86bd71cf2b61a4915ea6b46c35b10a831
Author: Jarek Potiuk <[email protected]>
AuthorDate: Mon Nov 13 23:33:23 2023 +0100

    Add instructions on how to verify sources for PMC members (#101)
    
    * Add instructions on how to verify sources for PMC members
    
    * Update dev/README_RELEASE_CLIENT.md
    
    Co-authored-by: Hussein Awala <[email protected]>
    
    * Update dev/README_RELEASE_CLIENT.md
    
    Co-authored-by: Hussein Awala <[email protected]>
    
    * Update dev/README_RELEASE_CLIENT.md
    
    Co-authored-by: Hussein Awala <[email protected]>
    
    ---------
    
    Co-authored-by: Hussein Awala <[email protected]>
---
 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..9ad59fe 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 OpenAPI 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 described 
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 [email protected], 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

Reply via email to