lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Itamar Syn-Hershko <>
Subject Re: Moving Lucene.NET to .NET Core
Date Fri, 11 Mar 2016 11:09:48 GMT
Hi Connie,

That's great news, thanks!

Please base your work on the master branch here: We will fix the wording on the
website, thanks for noticing.

Building via Lucene.NET.sln should work - can you let us know if it doesn't?

With regards to release dates and priorities - we currently don't have any
ETA since development is currently going on very slowly. The plan was to
finish fixing the last of the failing tests in Lucene.NET Core, complete
porting the major subprojects (e.g. Analysis) with tests, and then approach
compiling on .NET Core. Can you help us progress based on this roadmap, or
are your resources limited to compiling on .NET Core?

As for PRs - do you have an estimation of the amount / scope of changes
required? is the result going to be another project or the same codebase
compiling on .NET Core?

Thanks again for joining us in this effort!


Itamar Syn-Hershko | @synhershko <>
Freelance Developer & Consultant
Lucene.NET committer and PMC member

On Fri, Mar 11, 2016 at 12:45 AM, Connie Yau <> wrote:

> Hi all,
> Our team is working to make Lucene.NET run on .NET Core and was wondering
> if anyone else was working on this or would it be alright if we started
> this effort?
> Also, I was hoping that someone could answer a few questions I have about
> this project:
> 1.       What branch should we be basing our effort on?
> *         In Community<>, the
> documentation says "Most work currently happens on the branch named
> branch_4x<
> but it looks like the latest commits are in `master`
> 2.       How do we build this project?
> *         I read Build System & Scripts<
> but there doesn't appear to be a build.cmd in the repository<
> 3.       What is the expected release date for Lucene.NET v4.8?
> 4.       Regarding pull requests, is the preference for incremental
> changes (ie. Updating a set of APIs from one to another) or to have a large
> pull request (ie. Moving to run on .NET Core with all the associated
> project/code changes)?
> Thanks!
> Connie Yau

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message