-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap v4.* release #391
Comments
The roadmap doc is here and i think is still relevant https://shazwazza.github.io/Examine/developerguides/roadmap.html But that said, those 4 items are optional and could certainly come in later versions. There are PRs for these but are either incomplete or need reviving
Without feedback from the community, it is difficult to know if v4 is 'stable'. There's been no reported issues apart from one: If you have feedback on v4, it would be great to get some of it listed here (good or bad, etc...) I will certainly merge v3 up to v4 :) There's some active work/fixes in v3 that should be ready to be shipped soon and then I can merge up to v4 and get another beta of 4 out. |
Happy to discuss a revival. As far as I'm aware, all those prs are complete / pending review. |
@Shazwazza I won't open a new issue just for that question. |
Hi all, sorry for the radio silence here. Several people have been using 4 beta in the wild with great success but there are still some outstanding PRs/Issues to resolve. I'm also awaiting a few community members feedback, namely @callumbwhyte ;) to provide some insights into all the changes and what might be made simpler. Then - there's a gigantic amount of work being done in Lucene.Net right now to get it to a point where we can ship an RTM v4. There's quite a few breaking changes in the current beta so I'm hesitant to ship this now and then have to ship another major to cater for the breaking changes in the Lucene RTM release. Then - there's the Umbraco RFC for search which needs further details since potentially one of the requirements will be facets and I need to ensure that this all aligns with those requirements. Feel free to use v4 in prod, many people are doing just that. |
Rather a question since I don't know how I would have to reach out.
For one of our clients I'm looking to upgrade U8 towards U13.
They make use of BoboFacets so I kind of need to switch towards this version.
It has only been released as pre-release (almost a year), can it be considered stable by now?
Any plans on backtracking new changes of the v3.* version towards the v4.*?
Main change I'm looking towards is the new handling of corrupt indexes.
The text was updated successfully, but these errors were encountered: