[hibernate-dev] [Search] Future of branch 3.4.x

Sanne Grinovero sanne at hibernate.org
Mon Jul 18 06:04:56 EDT 2011


This is my proposal of commits to backport:

https://hibernate.onjira.com/browse/HSEARCH-741 (fix a NPE)
https://hibernate.onjira.com/browse/HSEARCH-780 (contributed bugfix
around Dirty analysis of collections)
https://hibernate.onjira.com/browse/HSEARCH-779 (programmatic mapping
API missing feature)

This is a nice to have, since we're going through the effort of doing
the release I'd propose to include it as well:
https://hibernate.onjira.com/browse/HSEARCH-754 (expose a
configuration option useful for Infinispan integration)

This one needs coding : HSEARCH-745 (Hardy, a faceting issue)

This is already in 3.4.x branch:
https://hibernate.onjira.com/browse/HSEARCH-744

Now if anyone has the time to cherry pick the appropriate commits,
I'll volunteer to review the pull request.
Then I'll wait for Hardy to see if he can fix the faceting issues on
both branches before actually starting the release.. Hardy could you
review the faceting issues and see which ones should go in 3.4.1 by
marking them on JIRA (if any other than HSEARCH-745) ?

Cheers,
Sanne



2011/7/18 Hardy Ferentschik <hardy at hibernate.org>:
> +1 I am also fine with back porting important fixes. But we have to be
> careful how much time we invest.
> Preferably we should focused on "contained" bugs/features.
>
> --Hardy
>
> On Mon, 18 Jul 2011 10:43:20 +0200, Emmanuel Bernard
> <emmanuel at hibernate.org> wrote:
>
>> I'm fine with cherry-picking / backporting the most important fixes and
>> releasing a 3.4.1. We are not going to release Hibernate Search 4 that soon.
>>
>> Sanne, could you list the most important issues to backport and we can
>> share the work amongst the team.
>>
>



More information about the hibernate-dev mailing list