curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Blum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-406) The CURATOR-3.0 branch should become master
Date Tue, 02 May 2017 19:55:04 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993606#comment-15993606
] 

Scott Blum commented on CURATOR-406:
------------------------------------

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)

Mime
View raw message