NightOwl888 commented on issue #562: URL: https://github.com/apache/lucenenet/issues/562#issuecomment-979930616
Thanks for the report. We are no longer supporting Lucene.NET 3.0.3 and the original team that ported it is no longer involved in the project. But this is primarily because all of our effort is going into 4.8.0 and we haven't looked into what it would take to resurrect 3.0.3 to begin patching it. ## Option 1 - Patch 3.0.3 Yourself According to the [3.0.3 release blog post](https://blogs.apache.org/lucenenet/entry/lucene_net_3_0_3), the tag that corresponds to it is [Lucene.Net_3_0_3_RC2_final](https://github.com/apache/lucenenet/tree/Lucene.Net_3_0_3_RC2_final). Do note that there are several 3.x branches which may be patched beyond that tag, but I haven't looked into what these patches are fixing, nor have they been verified: 1. [3.0.3 (branch - has commits after the 2012-10-26 release date)](https://github.com/apache/lucenenet/tree/3.0.3) 2. [3.0.3-2 (branch - last commit 2012-09-27)](https://github.com/apache/lucenenet/tree/3.0.3-2) 3. [branch_3x (branch - has commits after the 2012-10-26 release date)](https://github.com/apache/lucenenet/tree/branch_3x) 4. [branch_3.0x (branch - last commit 2014-09-07)](https://github.com/apache/lucenenet/tree/branch_3.0x) There are also several patches that RavenDB has done to 3.0.3 in their own fork: - https://github.com/ravendb/lucenenet If you are willing to do the footwork to figure out which of these options best corresponds to the 3.0.3 release and/or verify any patches to the branch that should go into another release, we could make sure it gets released and then we would have a way to continue patching it. Do note that the `.sln` files are a bit hard to find. They are in the [build folder](https://github.com/apache/lucenenet/tree/Lucene.Net_3_0_3_RC2_final/build). No objections if you wish to change this to a single `.sln` file with the latest `.csproj` project file format, but we probably don't want to go down the road of trying to support .NET Standard/.NET Core/.NET 5/.NET 6 due to the amount of complexity involved. Note also that it is an Apache requirement that the project must build and be testable via command line in order to [create a release](https://www.apache.org/legal/release-policy.html). To make it clear that this is still a patched 3.0.3 build, it should be versioned 3.0.3._n_, where _n_ increments with each release. ## Option 2 - Upgrade to 4.8.0-beta00015 I don't know if all of those components support 4.8.0-beta00015, but if so, I would recommend upgrading because we can definitely patch 4.8.0 and will be able to continue supporting it in the future. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
