[
https://issues.apache.org/jira/browse/AIRFLOW-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291468#comment-15291468
]
Chris Riccomini commented on AIRFLOW-135:
-----------------------------------------
I'm +1 on cutting branches for releases (instead of tags).
I'm also +1 on deleting dead branches, but could you post a list of the
proposed branches to delete so we can allow people time to notify if they have
a branch that they don't want deleted?
> Clean up git branches (remove old + implement versions)
> -------------------------------------------------------
>
> Key: AIRFLOW-135
> URL: https://issues.apache.org/jira/browse/AIRFLOW-135
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Jeremiah Lowin
> Priority: Minor
> Labels: git
> Fix For: Airflow 1.8
>
>
> We have a large number of branches in the git repo, most of which are old
> features -- I would bet hardly any of them are active. I think they should be
> deleted if possible. In addition, we should begin using branches (as opposed
> to tags) to allow easy switching between Airflow versions. Spark
> (https://github.com/apache/spark) uses the format {{branch-X.X}}; others like
> Kafka (https://github.com/apache/kafka) simply use a version number. But this
> is an important way to browse the history and, most importantly, can't be
> overwritten like a tag (since tags point at commits and commits can be
> rebased away).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
