Hi everyone, Please save your work and commit to right branch by end of today, we will do branch rename tonight. For people forked from specify branch, please add git upstream with right branch after rename.
And, please help to clean up unused branch from core repo. Thank you very much. Best Regards! --------------------- Luke Han On Wed, Sep 2, 2015 at 10:05 PM, Luke Han <[email protected]> wrote: > Hi community, > As one action after v1.0 release, we will rename existing branch to > new one as KYLIN-987 described. > Please make sure you have submitted changes with right branch, > If your repo is forked from current branch, please make sure update > upstream using git command. > > Will send out notification when we do the rename (target: end of this > week). > > Thanks. > > Luke > > > Best Regards! > --------------------- > > Luke Han > > On Wed, Sep 2, 2015 at 10:48 AM, Shaofeng SHI (JIRA) <[email protected]> > wrote: > >> >> [ >> https://issues.apache.org/jira/browse/KYLIN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726647#comment-14726647 >> ] >> >> Shaofeng SHI commented on KYLIN-987: >> ------------------------------------ >> >> +1; We need keep the branch name consistent with our release versions; >> As we're going to release 1.x, the 0.7 branch should be renamed to 1.x soon. >> >> > 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: v0.8.1, v1.1 >> > Reporter: hongbin ma >> > Assignee: hongbin ma >> > >> > 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) >> > >
