You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/11/17 11:18:50 UTC

[GitHub] [airflow] potiuk commented on pull request #27726: Provider fixups for 22-nov release

potiuk commented on PR #27726:
URL: https://github.com/apache/airflow/pull/27726#issuecomment-1318483330

   This is cool you do it :). Great to get someone else looking at it "seriously" :)
   
   Two comments:
   
   1) this PR should be continuously rebased until we release the previous wave, we then remove those providers that will need a new version and we will do new RCs from that
   
   2) after releasing and tagging current providers you will need to rebase this one to main, and run `breeze release-management prepare-provider-docuementation cncf.kubernetes jdbc asana google grpc yandex` (and all others. This does the following:
   
   - it asks you for each changed providers to classify changes that were done in the meantime - in some cases this will be "doc only change" but in some others we will need to bump/change a new version of the provider in question  
   - it will regenerate COMMITS.rst 
   - it will automatically append the changes since last released that were merged in main to CHANGELOGs  - this way any changes that were merged between, will not be forgotten - you will get them regenerted in a new section with the right comment and before adding/committing changes we should adjust CHANGELOG
   
   This is the process I've been following so far and it works very well IMHO. 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org