I hope for 0.15.0 we can get more people to install the release candidates in production -- I think probably a lot of people wait for a final release before doing that, but the additional testing really helps. At Imply we definitely have additional stress testing planned (in fact we've already installed the 0.15.0-incubating branch in _our_ production environment and have started to bang on it). The more of that we can get, the better, especially since not all sites use all features, so you need a few sites to get good coverage.
On Fri, May 10, 2019 at 10:36 AM Slim Bouguerra <bs...@apache.org> wrote: > It sounds like we are doing release after release with out enough time to > validate candidates, in the long run this might hurt adoption. > > On Fri, May 10, 2019 at 08:44 Gian Merlino <g...@apache.org> wrote: > > > It sounds like a plan to me. > > > > On Thu, May 9, 2019 at 6:53 PM Clint Wylie <cwy...@apache.org> wrote: > > > > > I know 0.14.1-incubating just released, and the 0.15.0-incubating > branch > > > has already been cut, but > > > https://github.com/apache/incubator-druid/issues/7607 which was > > introduced > > > in 0.14.1-incubating seems like a pretty ugly issue, so I'm throwing > > > together a 0.14.2-incubating with the fix and a couple of other bug > fixes > > > for result level cache. > > > > > > fixes: > > > https://github.com/apache/incubator-druid/pull/7619 > > > https://github.com/apache/incubator-druid/pull/7614 > > > https://github.com/apache/incubator-druid/pull/7624 > > > > > > I think the turn around on getting 0.14.2-incubating out might be a lot > > > quicker than the timespan it will take us to validate, finalize, and > vote > > > on 0.15.0-incubating. > > > > > > Thanks, > > > Clint > > > > > >
