If the current code base is 0.3.0 was there a 0.2.4 release cut? I would very much like to see one release done with everything that is in blur today just to have something newer than 0.2.3 to work with in the meantime. Is that acceptable before kicking any of these much desired efforts off?
On Wed, Nov 11, 2015 at 11:10 AM, Aaron McCurry <[email protected]> wrote: > Yeah the current code base version is on 0.3.0. So we could just make the > changes now is this version. > > I would like to start moving forward with these issues as soon as > possible. I will give it a day or so for anyone else to chime in but I > think we can assume that the renaming issues should move forward. > > Aaron > > On Wednesday, November 11, 2015, Tim Williams <[email protected]> > wrote: > > > On Wed, Nov 11, 2015 at 2:30 PM, Aaron McCurry <[email protected] > > <javascript:;>> wrote: > > > Since Blur was created it has been about big data. Large indexes, > large > > > clusters, large ingest rates, fast queries, etc. Over the years > features > > > have been created that add more database like properties. In concept > > this > > > was a good thing, but those decisions have made it difficult to > > understand > > > and for Blur to perform well under those database like constraints. > > > > > > I believe now is the time for the project to regain focus on what it > does > > > well. I have created some tickets that will begin the transformation > > into > > > a more focused project. > > > > This is great, thanks Aaron! For context, I assume these are for a > > post-0.2.4? > > > > > https://issues.apache.org/jira/browse/BLUR-442 > > > https://issues.apache.org/jira/browse/BLUR-443 > > > https://issues.apache.org/jira/browse/BLUR-444 > > > > Wahoo! to all three! > > > > Will ask clarifying questions on the others in JIRA... > > > > --tim > > >
