NightOwl888 commented on issue #778:
URL: https://github.com/apache/lucenenet/issues/778#issuecomment-1344250385

   That is correct for the most part. There have been several newer issues 
added that don't have a 4.8.0 milestone that probably should, though.
   
   Trying to determine exactly what is blocking the release requires analysis 
to work out, which makes a list like that a lot of work to maintain. For sure 
we have a blocker if:
   
   1. The solution to the issue requires a [breaking API 
change](https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/breaking-changes#source-breaking-change).
 See [Changes that affect 
compatibility](https://learn.microsoft.com/en-us/dotnet/core/compatibility/).
   2. The solution to the issue requires a [breaking behavioral 
change](https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/breaking-changes#behavior-breaking-change).
   3. It is a priority bug
   
   > NOTE: In general, we shouldn't have any breaking binary changes because 
for the most part we are using the same binary formats as Lucene. That said, 
there is an open task to add [tests to verify 2-way 
compatibility](https://github.com/apache/lucenenet/issues/270), as this hasn't 
been run for several years and there have been a large number of changes since 
then.
   
   If the feature requires an additive change, it can generally wait unless the 
priority is high (normal and low priority are not blockers, but are "could 
haves" that would be accepted if submitted as PRs).
   
   [Reviewing tests](https://github.com/apache/lucenenet/issues/259) is 
blocking the release. The tests we have reviewed so far have revealed that we 
are missing asserts and other test features. They have also revealed several 
other usability issues that need to be addressed, and I suspect the review may 
bring up a few more of those issues.
   
   And of course, making [ICU4N](https://github.com/NightOwl888/ICU4N) stable 
is also still a blocker (unless we opt to delay release of everything that 
depends on it). All of our other dependencies are stable, but some have 
up-for-grabs tasks that would be nice additions to have.
   
   In general, anything that is using the [Future 
milestone](https://github.com/apache/lucenenet/milestone/4) can wait until 
after the release.
   
   
   


-- 
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: dev-unsubscr...@lucenenet.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to