Testing it within AS is not my primary reason for agreeing to this beta.
As I said we clearly have a big enough body of work (113 issues) to go
ahead with the next beta.
>From my dev perspective the JPA criteria stuff is getting *very* close
to done (even the tck numbers there are looking great)
The cutoff for getting external libs integrated into the AS trunk for M2
is Jan 31. I'd consider holding it open a bit longer for Hibernate (at
most a week) if it meant getting feature complete and stable JPA2 impl.
I wouldn't want to hold it open though to go from 75% complete to 85% or
some s
We certainly have enough fixes (currently 113 [1]) in to warrant another
release to give people a chance to test these fixes out.
As far as inclusion in an AS release, well that depends on when the
"component cutoff" date is for this M2. Do you know for certain?
[1]
http://opensource.atlassian.c
Steve,
Is this expected to be the final build for AS M2? My vote is to build
3.5.0-Beta-3 soon and another (more JPA-2 feature complete) build in
February (for inclusion in AS M2). I don't care what we label the
February build (3.5.0-Beta-4 or 3.5 final).
An alternative would be to hold off on
I went ahead and set up this next release in JIRA (3.5.0-Beta-3) and
moved all unresolved issues to the 3.5 working release. If there is
anything you need in 3.5.0-Beta-3 that is not there speak up now (by
scheduling the corresponding JIRA issue) or forever hold your piece :)
On Thu, 2010-01-07
Sure, let's do one at the beginning of next week.
On Wed, 2010-01-06 at 18:11 +0100, Emmanuel Bernard wrote:
> Steve,
> Do you think there is enough material / bug fix to cut another beta
> for inclusion in AS 6 M2?
> Something like a 2 weeks target.
>
>
> On my side that would make sense to pu
