10:57 a.m.
Hello,
Are we going to release a 3.4.1 version of Hibernate Search at some point?
There are some community members asking if there is any plan, and if
there's an expected timeframe.
There where some issues with the new features in 3.4.0, the most
urgent ones where quickly reported and fixed since that people is
using 3.5.0 snapshots.
Some other fixes in the faceting are are still to be done, but I
remember Hardy mentioning they should be easy.. ideally we could merge
these too, iff there's such an intention.
I had created a 3.4.x branch only recently from the 3.4.0 release tag:
this means it's not containing all of the fixes which are in master.
Cheers,
Sanne
3:43 a.m.
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.
Emmanuel
On 16 juil. 2011, at 17:57, Sanne Grinovero wrote:
Hello,
Are we going to release a 3.4.1 version of Hibernate Search at some point?
There are some community members asking if there is any plan, and if
there's an expected timeframe.
There where some issues with the new features in 3.4.0, the most
urgent ones where quickly reported and fixed since that people is
using 3.5.0 snapshots.
Some other fixes in the faceting are are still to be done, but I
remember Hardy mentioning they should be easy.. ideally we could merge
these too, iff there's such an intention.
I had created a 3.4.x branch only recently from the 3.4.0 release tag:
this means it's not containing all of the fixes which are in master.
Cheers,
Sanne
3:49 a.m.
+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(a)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.
5:04 a.m.
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(a)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(a)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.
>
4907
days inactive
4909
days old
3 comments
3 participants
participants (3)
-
Emmanuel Bernard -
Hardy Ferentschik -
Sanne Grinovero