lucenenet-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [5/8] lucenenet git commit: Updated with the latest status
Date Thu, 20 Jul 2017 21:49:26 GMT
Updated with the latest status


Branch: refs/heads/master
Commit: 40e919057b369c78e5b4e4c3db5d36dec1d55d53
Parents: aa849d8
Author: Shad Storhaug <>
Authored: Fri Jul 21 03:56:55 2017 +0700
Committer: Shad Storhaug <>
Committed: Fri Jul 21 03:56:55 2017 +0700

---------------------------------------------------------------------- | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ b/
index 1ace445..226e681 100644
--- a/
+++ b/
@@ -38,7 +38,6 @@ Note that even though we are currently a port of Lucene 4.8.0, we recommend
 ### Pending being ported from scratch (code + tests)
-* [Lucene.Net.Analysis.ICU](
- See [JIRA issue 566](
 * [Lucene.Net.Analysis.Kuromoji](
- See [JIRA issue 567](
 ### Pending being ported from scratch (code + tests), but have additional dependencies that
also either need to be sourced from the .NET ecosystem or ported.
@@ -74,6 +73,7 @@ and <
 * Making demos and tutorials, blogging about Lucene.Net, etc. (and providing feedback on
how we can make the API better!). If you write a helpful Lucene.Net post on your blog, be
sure to let us know so we can link to it.
 * Helping out with documentation. We are still trying to make the API docs easily navigable
(see #206), and there are many files that are not formatted correctly (links not appearing,
tables not very readable, etc). Also, we need help getting all of the Java-related documentation
converted to use .NET methodologies.
+* Fixing TODOs. There are several TODOs throughout the code that need to be reviewed and
action taken, if necessary. Search for `LUCENENET TODO|LUCENE TO-DO` using the regular expression
option in Visual Studio to find them. Do note there are a lot of TODOs left over from Java
Lucene that are safe to ignore.
 * Reviewing code. Pick a random section, review line by line, comparing the code against
the [original Lucene 4.8.0 code](
Many of the bugs have been found this way, as the tests are not showing them. Let us know
if you find anything suspicious on the [dev mailing list](
or submit a pull request.
 * Optimizing code. During porting we have ended up with some code that is less than optimal.
We could use a hand getting everything up to speed (pun intended).
 * Helping update the API, or at least just providing feedback on what is important. There
are several things on our radar, like integrating something like [Lucene.Net.Linq](
directly into our project, [converting the remaining public-facing iterator classes into `IEnumerator<T>`](
so they can be used with foreach loops, adding extension methods to remove the need for casting,

View raw message