[ 
https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Blum resolved CURATOR-406.
--------------------------------
    Resolution: Fixed

- master is on 3.0 now

- I left a CURATOR-2.0 branch where master was, you could create a master-2.0 
there if you object to the naming

- Consider deleting the CURATOR-3.0 branch at some point

> The CURATOR-3.0 branch should become master
> -------------------------------------------
>
>                 Key: CURATOR-406
>                 URL: https://issues.apache.org/jira/browse/CURATOR-406
>             Project: Apache Curator
>          Issue Type: Task
>          Components: General
>    Affects Versions: 3.3.0, 2.12.0
>            Reporter: Jordan Zimmerman
>            Assignee: Scott Blum
>
> Currently, we have two main git branches, {{master}} (corresponding to 
> Curator 2.x) and {{CURATOR\-3.0}}. {{master}} should become {{master\-2.0}} 
> and {{CURATOR\-3.0}} should become {{master}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to