I don't think I'm as hard core on this as Neal, but remember: the
history of the Lucene.NET project is that all the intellectual work, all
the understanding of search, all the new features come from the Lucene
Java folks. Theirs is an immensely respected project, and I trust them
to add new
Can I just plug in my bit and say I agree 100% with what Moray has outlined
below.
If we move away from the line by line port then over time we'll loose out on
the momentum that is Lucene and the improvements that they make.
It is only if the Lucene.NET community has expertise in search, a
As someone from the nhibernate project
We stopped following hibernate a while ago, and haven't regretted it
We have mire features, less bugs and better code base
Sent from my Windows Phone From: Rory Plaire
Sent: Thursday, June 30, 2011 19:58
To: lucene-net-dev@lucene.apache.org
Subject: Re:
NHibernate has a much bigger community and more active devs afaict.
The proposed changes as I understand them are not about changing class
structure or APIs, but merely touch hunks of code and rewrite them to
use better .NET practices (yield, generics, LINQ etc). In conjunction
with a move
Michael,
You interpret the report as whoever commits code wins? But when I look at it,
I see a lof of talk, no work. .Net community is not interested in
contributing.
I really don't understand what hinders people to work on Lucene.Net. As I did
for 2.9.4g, grab the code, do whatever you want on
A) I don't to want to commit anything thats going to piss alot of people
off,
B) I don't want to spend time/waste time on modifications that are going
to be rejected.
What I've learnt from Apache Way is creating a JIRA issue if you are
hesitant.
If no one answers in a reasonable
DIGY - Re: Why do I wait.. That's mostly because I intend to make some deep
changes, which would make merging the 2.9.4g branch back to trunk difficult.
So, it's easier to merge those changes first. Also, I won't have enough time
to make my changes until a little way in the future, but probably do
Scott -
The idea of the automated port is still worth doing. Perhaps it makes sense
for someone more passionate about the line-by-line idea to do that work?
I would say, focus on what makes sense to you. Being productive, regardless
of the specific direction, is what will be most valuable. Once
Michael -
If you bring those changes from git into a branch in SVN, we can help with
it. It doesn't have to be complete to be committed. :)
Regarding A (angering people)/B (being rejected)/C (feeling comfortable)/D
(getting over it)...
a) Making progress is more important than keeping everyone
I can not say I like this approach, but till we find an automated way(with good
results), it seems to be the only way we can use.
DIGY
-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Friday, July 01, 2011 12:43 AM
To: lucene-net-dev@lucene.apache.org
Subject:
So, veering towards action - are there concrete tasks written up anywhere
for the unit tests? If a poor schlep like me wanted to dig in and start to
improve them, where would I get the understanding of what is good and what
needs help?
-r
On Thu, Jun 30, 2011 at 3:29 PM, Digy digyd...@gmail.com
11 matches
Mail list logo
