[
https://issues.apache.org/jira/browse/LUCENENET-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834329#action_12834329
]
Michael Garski commented on LUCENENET-336:
------------------------------------------
I like the idea of tagging with 2.9.1 and then getting the 2.92 patches in
order. Java Lucene has a release candidate for 2.9.2 at this time.
> Shortcut for Lucene.NET 2.9.1 --> 2.9.2
> ---------------------------------------
>
> Key: LUCENENET-336
> URL: https://issues.apache.org/jira/browse/LUCENENET-336
> Project: Lucene.Net
> Issue Type: Improvement
> Reporter: Digy
> Priority: Trivial
> Attachments: Lucene.NET.2.9.2.patch, Lucene.NET.2.9.2.patch,
> Lucene.NET.2.9.2.patch, Lucene.NET.2.9.2.patch, Lucene.NET.2.9.2.patch,
> Lucene.NET.2.9.2.patch
>
>
> This issue contains all necessary updates to upgrade to 2.9.2.
> LUCENENET-334: [LUCENE-2086] When resolving deletes, IW should resolve in
> term sort order
> LUCENENET-333: [LUCENE-2095] Document not guaranteed to be found after write
> and commit
> LUCENENET-332: [LUCENE-2092] BooleanQuery.hashCode and equals ignore
> isCoordDisabled
> LUCENENET-331: [LUCENE-2190] CustomScoreQuery (function query) is broken
> (due to per-segment searching)
> +
> NIOFSDirectory (NullImplementation as in 2.4.0)
> +
> Assembly.cs
> All issues
> (https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342) are
> fixed.
> All Nunit test pass.
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
