Mostly done:
I've split 3.2 into:
- Beta1: existing features + documentation
- Beta2: bug fix and stabilization
- Beta3: next round of features
- CR1: fix what has to be fixed.
Depending on when Beta2 happens and how close Hibernate 3.5 final is,
we could cut 3.2 here and backport to JPA 1.
I have not reviewed open unscheduled bug reports yet. If someone want
to pre sort them, be my guest.
On 31 oct. 09, at 01:13, Sanne Grinovero wrote:
Yes I guess a beta could be released pretty soon.
You and Emmanuel should set some milestones?
It would be helpful if you could create some more releases in JIRA,
like a beta and a CR, so that we can move really important issues to
the first beta and postpone the others.
You could start playing with the integrated Greenhopper (see
Agile->Planning Board).
Sorry for the previous answer being empty, got wrong shortcut on the
phone.
Sanne
2009/10/30 Hardy Ferentschik <hibernate(a)ferentschik.de>:
> Hi,
>
> I was just wondering whether we have reached a decision yet for the
> 3.2.0
> release of HSearch?
> Some of the issues scheduled for this release and assigned to me do
> not
> seem to be that important.
> I will go through them in Jira.
>
> I will also try to finish the DynamicBoost documentation over the
> weekend.
> It will be another small
> step towards the next release of HSearch :)
>
> --Hardy
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>