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 2019/11/08 12:27:53 UTC

[GitHub] [airflow] potiuk commented on issue #6523: [AIRFLOW-5873] KubernetesPodOperator fixes and test

potiuk commented on issue #6523: [AIRFLOW-5873] KubernetesPodOperator fixes and test
URL: https://github.com/apache/airflow/pull/6523#issuecomment-551707439
 
 
   Hey @ddelange. I saw your comment - while writing this. Cool that you are working on it :). 
   The process we have now is that we want to make sure 1.10.* does not diverge from master so we implement all the changes as PRs to master and cherry-pick them (committers do it usually) if we decide to back-port them to v1-10-test and then when tests pass we move then to v1-10-stable branch.  However we must make sure that those changes are backwards compatible in 1.10 (unless we have very good reason to drop compatibility).
   
   So if those changes are based on some existing commit in master it's better to pin-point this and cherry pick from there. If those are new changes, they should be added as PR to master and cherry-picked after it gets merged in master. 
   
   I think it's not described very well, but we are just in a process of updating contributor's documentation with Google Season of Docs and I think it's a good point to add to CONTRIBUTING.rst (@efedotova -> maybe we can add it to the workflows we were discussing about)
   
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services