It think it's a good idea to release 0.7 branch as Kylin 1.0 The reasons are threefold:
1. 0.7 branch is getting mature in cubing job scheduling, REST server, query engine, even documents. Complete OLAP solution can be build with it. 2. 0.7 branch contains most of bugs in latest code. 3. 0.8 branch is too early to be announced as a release On Thu, Aug 6, 2015 at 11:12 AM, Luke Han <[email protected]> wrote: > Hi Seshu, > No, release current 0.7.3 as v1.0. 0.8 still to early to release since > there are many refactoring. it should be mark as 2.0;-) > > Thanks. > > Luke > > > Best Regards! > --------------------- > > Luke Han > > On Thu, Aug 6, 2015 at 1:46 AM, Adunuthula, Seshu <[email protected]> > wrote: > > > Luke, > > > > Are you thinking of renaming the current 0.8 branch as 1.0? > > > > Regards > > Seshu > > > > On 8/5/15, 8:21 AM, "Luke Han" <[email protected]> wrote: > > > > >Hi all, > > > As several rounds testing and 2 releases, we are comfortable to say > > >the current > > >version of Kylin is quite stable than the beginning when it join > > >incubating. > > > With some cases, not only inside eBay also other deployments on > > >production outside eBay, it already proved the quality and performance > of > > >Apache Kylin. > > > > > > So I would like to raise a discussion here to make next release to > > >*v1.0 > > >*(0.7.3-snapshot now) which should be released in August, since the > > >maturity of code base, product is good enough. > > > > > > Please kindly help to leave your inputs and comments here. > > > > > > Thanks. > > > > > > > > > > > >Best Regards! > > >--------------------- > > > > > >Luke Han > > > > > -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
