Gagan,

No hard deadline, but maybe we should create one?  I would like to say a
couple of weeks?

Aaron


On Sun, Mar 17, 2013 at 1:23 AM, Gagan Juneja <[email protected]>wrote:

> Hi Aaron,
> That's a great idea!
> Do we have decided on any deadline for 0.1.5 release?
>
> Regards,
> Gagan
>
> On Sunday, March 17, 2013, Aaron McCurry wrote:
>
> > Thanks Tim, I think that we should create JIRA issues for these working
> > toward a 0.1.5 release.  I can do that or other want before I get to them
> > that's cool.  Also we should branch 0.1.4 to create 0.1.5.
> >
> > Also the new metrics will be easy to drop in, so I think that we should
> add
> > that as well.
> >
> > Thanks,
> > Aaron
> >
> >
> >
> > On Sat, Mar 16, 2013 at 5:09 PM, Tim Williams <[email protected]
> <javascript:;>>
> > wrote:
> >
> > > On Sat, Mar 16, 2013 at 2:10 PM, Aaron McCurry <[email protected]
> <javascript:;>>
> > wrote:
> > > > -Lucene 4.2 Upgrade
> > > >    This is the big feature, but I spent a lot of time a few weeks ago
> > > > testing the resource management (InputIndex clones, Buffers, File GC,
> > > etc)
> > > > and geting it all working.  So I feel really good about this code.
> > > >
> > > > -Automatic Slab configuration (Easy to integrate code)
> > > >    This is simple but makes things easier to configure
> > > >
> > > > -Super Query Parser (Easy to integrate code)
> > > >    This gives explicit control over the super queries
> > > >
> > > > There will probably be a couple of more things to add but most are
> > going
> > > to
> > > > be drop in replacements of existing code.
> > > >
> > > > Anything else that you can think of that would be good backport?
> > >
> > > Looks good, unless the new metrics stuffs is solid enough?  I could
> > > take a stab at backporting the new auto slab configs if you want?
> > >
> > > --tim
> > >
> >
>

Reply via email to