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 2020/06/22 14:08:21 UTC

[GitHub] [airflow] potiuk edited a comment on issue #9351: Consider renaming master branch to something less offensive

potiuk edited a comment on issue #9351:
URL: https://github.com/apache/airflow/issues/9351#issuecomment-647542295


   Agree. While I am all for changing - I think we can wreak havoc by haste changes here. 
   
   An Idea: Why don't we continue working on 2.0 in master and once we start 2.1 work we can create "development" branch and rather than switching to master immediately we will simply ask everyone to move their PR to "development" for their PRs if they want to get them merged. This way we can do it gradually and naturally. And it's a good opportunity for a "clean" start for 2.1
   


----------------------------------------------------------------
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