Done.  For future reference to tweeting things with dots.  We have to use
ascii with Lucene.Net on tweets. Otherwise twitter will transform the
"Lucene.Net" text into a link that points to its Java counterpart.

Lucene.Net



On Fri, Apr 13, 2012 at 12:37 PM, Christopher Currens <
currens.ch...@gmail.com> wrote:

> Okay, I looked over the properties, and after a few slight changes, I think
> they nearly all of them are within reason (either doing a
> small mathematical computation or null check).  I'm actually very eager to
> start hearing feedback on the API changes.  I think most people will be
> able to figure it out easily.
>
> It would also be nice if people could find bugs we could fix before
> releasing it.  Actually, it would be nice if people knew there was a 3.0.3
> version  coming out.  So, I say go for it.
>
>
> Thanks,
> Christopher
>
> On Thu, Apr 12, 2012 at 6:14 PM, Christopher Currens <
> currens.ch...@gmail.com> wrote:
>
> > Michael,
> >
> > Not quite yet.  I think I was overly aggressive with some of the
> > conversions I made with Get/Set functions to Properties, and I want to
> > revert any that I find do too much work back into a method.
> >
> > After that, I think most of the API changes left to make are fairly
> > minimal, and it would be nice to get some feedback from the community.
> >  Maybe I'll work on those properties tonight.
> >
> >
> > Thanks,
> > Christopher
> >
> >
> > On Thu, Apr 12, 2012 at 5:17 PM, Michael Herndon <
> > mhern...@wickedsoftware.net> wrote:
> >
> >> Chris, Prescotts, others awesome committers working on trunk,
> >>
> >> Do you wish the project to start attempting to gain attention for 3.0.3
> >> and
> >> possibly gain some community testing / wear and tear on it?
> >>
> >> Also are there any pressing matters you wish to gain more feedback on
> from
> >> the community?  Our twitter account has been too silent.
> >>
> >> -Michael
> >>
> >> P.S.  really great work on trunk.  I've been playing with the bits as
> time
> >> permits and might even use the upcoming release at work.  If I do, I'll
> >> put
> >> some time into contributing some docs / tutorials.
> >>
> >
> >
>

Reply via email to