[
https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993606#comment-15993606
]
Scott Blum edited comment on CURATOR-406 at 5/2/17 7:55 PM:
------------------------------------------------------------
Do you want the old master as {{master-2.0}} or {{CURATOR-2.0}} to match with
the current scheme that {{CURATOR-3.0}} suggests?
was (Author: dragonsinth):
Do you want the old master as `master-2.0` or `CURATOR-2.0` to match with the
current scheme that `CURATOR-3.0` suggests?
> 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)
