Sorry for the late follow up on this one.
Even after pruning JIRA of non-important issues targeted for 5.6 there
are still several ones open and I suspect it would take more than two
weeks. So while I would generally agree with Gunnar's suggestion to
try hard to not overlap work on active branches
Hi,
What's still missing from releasing 5.6 (compatible with ORM 5.0/5.1),
labelling the ES support as a "tech preview"?
I'd hope we could do such release rather quickly after you re-focus from
OGM to HSEARCH? Calling the ES support a "tech preview" will allow us to
release something a bit less p
On 11 August 2016 at 14:36, Guillaume Smet wrote:
> Hi Sanne,
>
> I had the same thought a few days ago. At Open Wide, we used to follow
> the ORM versions very closely and we usually had a corresponding
> Search version very soon.
>
> I agree we need to release something compatible with ORM 5.2 s
Hi Sanne,
I had the same thought a few days ago. At Open Wide, we used to follow
the ORM versions very closely and we usually had a corresponding
Search version very soon.
I agree we need to release something compatible with ORM 5.2 sooner
rather than later.
I understand your concern about bring
Hi all,
as you might be aware, ORM 5.2 made some rather radical internal work,
and the latest Hibernate Search releases aren't compatible.
So far, business as usual: we typically simply catch up on the next minor.
The problem is that normally Hibernate Search releases are time-boxed
- with us onl
