You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2015/09/07 14:21:46 UTC

[jira] [Updated] (KYLIN-987) Rename 0.7-staging and 0.8 branch

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

hongbin ma updated KYLIN-987:
-----------------------------
    Fix Version/s: v1.1
                   v2.0

> Rename 0.7-staging and 0.8 branch
> ---------------------------------
>
>                 Key: KYLIN-987
>                 URL: https://issues.apache.org/jira/browse/KYLIN-987
>             Project: Kylin
>          Issue Type: Improvement
>    Affects Versions: v2.0, v1.1
>            Reporter: hongbin ma
>            Assignee: hongbin ma
>             Fix For: v2.0, v1.1
>
>
> As we're planning to release the latest 0.7 branch as Kylin 1.0, previous branch naming conventions will be outdated. 
> Previously we had:
> *0.7-staging*: dev branch for 0.7 versions, this branch spawns releases like 0.7.1, 0.7.2, etc.
> *0.8* : dev branch for 0.8 versions, 0.8 is like the next generation Kylin (with streaming, spark support), it has fundamental difference with 0.7 version, which means any changes on 0.7 will not be merged to 0.8 anymore. So if your patch affects both of the branch, you should make patches for both branch.
> *master*: always point to the latest stable release(stable, but not up to date)
> I suggest that:
> * rename 0.7-staging to 1.x-staging, 1.x-staging will spawn releases like 1.0,1.1, etc.
> * rename 0.8-staging to 2.x-staging,  2.x-staging will spawn releases like 2.0, 2.1, etc.
> Please leave comments if you have uncommitted changes or you have other suggestions. If possible let's make the change in this week.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)