I've renamed following branches. 2.x-staging => master 1.x-staging => 1.3.x
Future releases (1.4, 1.5, ..) will fork from the master branch. On Thu, Mar 10, 2016 at 3:38 PM, Li Yang <[email protected]> wrote: > Thanks guys! > > Let me work. > > On Thu, Mar 10, 2016 at 2:06 PM, [email protected] <[email protected]> > wrote: > >> +1 >> and the roadmap should be included >> >> >> >> 中国移动广东有限公司 网管中心 梁猛 >> [email protected] >> >> From: Dong Li >> Date: 2016-03-10 14:00 >> To: dev >> Subject: Re: Back to one dev branch >> +1 >> >> >> then developers would got better experience on git repository. :) >> >> >> Thanks, >> Dong Li >> >> >> Original Message >> Sender:hongbin [email protected] >> Recipient:[email protected] >> Date:Thursday, Mar 10, 2016 13:57 >> Subject:Re: Back to one dev branch >> >> >> +1 pointing the latest dev branch is more intuitive for those who are not >> that familiar with Kylin dev. On Thu, Mar 10, 2016 at 12:37 PM, Li Yang >> [email protected] wrote: Hi all With the settling of 1.3.0 release, >> the development of 1.x-staging will come to a maintenance mode. New >> features have been and will go on in 2.x-staging, which is the main dev >> branch. So I'd like to take this chance to go back to a more common >> branch setup -- *let master be the main dev branch*. Most open source >> takes this approach I believe. This will fix things, like Git Pulse shows >> events on master which does not reflect our real activities currently. >> Also pull requests expect to be merged back to master so to be auto >> closed. Any thoughts? Yang -- Regards, *Bin Mahone | 马洪宾* Apache >> Kylin: http://kylin.io Github: https://github.com/binmahone >> > >
