The general direction should be to put most of the efforts on a v4 port (4.1 probably...) and to start finding pieces in the codebase we can easily isolate and .NET-ify. Mostly readers, writers, structures and conversions.
Re git on apache - I believe you should ask infra. On Tue, Dec 18, 2012 at 6:54 PM, Christopher Currens < [email protected]> wrote: > Don't think I've forgotten about this. While I have no idea how git under > Apache looks like, I have a lot of comments on Lucene 3.6 (and 4.0) that I > need to discuss on this mailing list directly relating to the porting work > and the future direction of lucene.net. I've had an email in my drafts > folder for about 3 weeks now but this time of year has been so busy I > haven't had a chance to finish it. Soon, though, I hope. > > > Thanks, > Christopher > > > On Sat, Dec 15, 2012 at 1:09 PM, Prescott Nasser <[email protected] > >wrote: > > > Hey Guys - I've been quietly working in the background on administrative > > stuff for a while. I really only have two things on my to-do list - - > What > > does git under apache look like? I can't remember who asked this, but I > > know I owe digging up the answer- Lucene 3.6 - planning, moving forward ( > > https://github.com/apache/lucene-solr/compare/5261b571...e4402c22c). Do > > we just want to start picking things off and committing them? Are there > > other refactoring issues we want to tackle with 3.6? We should make jira > > tickets and start tracking. Happy holidays everyone! ~Prescott > > >
