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 push the discrete but new > mapping / bug fixes out for trial. It also helps Hibernate Search > development (on Core snapshot ATM). > > > Emmanuel > > Begin forwarded message: > > > From: Brian Stansberry <brian.stansberry(a)redhat.com&gt; > > > > Date: 6 janvier 2010 17:38:37 HNEC > > > > To: jboss-development(a)lists.jboss.org > > > > Subject: Re: [jboss-dev] Further profling: Where should I focus? > > > > Reply-To: "JBoss.org development list" > > <jboss-development(a)lists.jboss.org&gt; > > > > > > > > > > > Any ETA on VFS3 being done and integrated with AS 6? > > > > > > > My guesstimate is very early in the M3 cycle (i.e. as soon as we > > open > > trunk to commits after M2). So mid-February. > > > > It's tempting to try for M2, but there's only 3.5 weeks left before > > component integration freeze, this is a big disruptive change and > > there > > are a couple issues to resolve: > > > > 1) Detecting modifications of exploded deployments: > > http://community.jboss.org/thread/146098 > > > > 2) This caching discussion, which IMHO should continue. It's legit > > to > > think again about what the intended use cases are for VFS and see if > > its > > API can be adjusted to more effectively handle those use cases. > > > > The MC team is going to be putting out a 2.2 alpha release soon; > > while > > that's being integrated in the AS and issues resolved over the next > > week > > it makes little sense to try and start pushing in VFS3. So let's > > use > > that time to resolve the modification detection issue and discuss a > > bit > > more about caching. By the end of next week we should have a > > clearer > > picture as to whether trying for M2 is feasible. > > > > -- > > Brian Stansberry > > Lead, AS Clustering > > JBoss by Red Hat > > _______________________________________________ > > jboss-development mailing list > > jboss-development(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jboss-development > > > >

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 building 3.5.0-Beta-3 for a few weeks (so we can get more JPA-2 features completed for AS M2). Scott On Thu, 2010-01-07 at 16:13 -0600, Steve Ebersole wrote: > 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 at 09:14 -0600, Steve Ebersole wrote: > > 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 push the discrete but new > > > mapping / bug fixes out for trial. It also helps Hibernate Search > > > development (on Core snapshot ATM). > > > > > > > > > Emmanuel > > > > > > Begin forwarded message: > > > > > > > From: Brian Stansberry <brian.stansberry(a)redhat.com&gt; > > > > > > > > Date: 6 janvier 2010 17:38:37 HNEC > > > > > > > > To: jboss-development(a)lists.jboss.org > > > > > > > > Subject: Re: [jboss-dev] Further profling: Where should I focus? > > > > > > > > Reply-To: "JBoss.org development list" > > > > <jboss-development(a)lists.jboss.org&gt; > > > > > > > > > > > > > > > > > > > Any ETA on VFS3 being done and integrated with AS 6? > > > > > > > > > > > > > My guesstimate is very early in the M3 cycle (i.e. as soon as we > > > > open > > > > trunk to commits after M2). So mid-February. > > > > > > > > It's tempting to try for M2, but there's only 3.5 weeks left before > > > > component integration freeze, this is a big disruptive change and > > > > there > > > > are a couple issues to resolve: > > > > > > > > 1) Detecting modifications of exploded deployments: > > > > http://community.jboss.org/thread/146098 > > > > > > > > 2) This caching discussion, which IMHO should continue. It's legit > > > > to > > > > think again about what the intended use cases are for VFS and see if > > > > its > > > > API can be adjusted to more effectively handle those use cases. > > > > > > > > The MC team is going to be putting out a 2.2 alpha release soon; > > > > while > > > > that's being integrated in the AS and issues resolved over the next > > > > week > > > > it makes little sense to try and start pushing in VFS3. So let's > > > > use > > > > that time to resolve the modification detection issue and discuss a > > > > bit > > > > more about caching. By the end of next week we should have a > > > > clearer > > > > picture as to whether trying for M2 is feasible. > > > > > > > > -- > > > > Brian Stansberry > > > > Lead, AS Clustering > > > > JBoss by Red Hat > > > > _______________________________________________ > > > > jboss-development mailing list > > > > jboss-development(a)lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/jboss-development > > > > > > > > > >

From my dev perspective the JPA criteria stuff is getting *very* close

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 such. The AS needs to enforce time-box discipline on itself. :) If you've got a substantial set of work completed, I'm all in favor of getting a new beta integrated ASAP. Better to surface any issues now than at the last minute. Also, it seems to me the integration testsuite in the AS for JPA2 needs beefing up; that work can start as soon as an impl with the features under test is integrated. If you think you're going to go past the Jan 31 deadline, I very much want another beta integrated soon. Going past Jan 31 cuts into the short (two week) window between component integration cutoff and turning over M2 to QE. That adds risk, so let's reduce that risk by seeing where we stand now. Note though that the latest Microcontainer release will be getting integrated into AS trunk in the next few days. That will likely disturb things for a few days. If the point of another beta is to test it in AS, holding off a few days is IMO wise. On 01/08/2010 08:39 AM, Scott Marlow wrote: > 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 building 3.5.0-Beta-3 for a few > weeks (so we can get more JPA-2 features completed for AS M2). > > > Scott > > On Thu, 2010-01-07 at 16:13 -0600, Steve Ebersole wrote: >> 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 at 09:14 -0600, Steve Ebersole wrote: >>> 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 push the discrete but new >>>> mapping / bug fixes out for trial. It also helps Hibernate Search >>>> development (on Core snapshot ATM). >>>> >>>> >>>> Emmanuel >>>> >>>> Begin forwarded message: >>>> >>>>> From: Brian Stansberry&lt;brian.stansberry(a)redhat.com&gt; >>>>> >>>>> Date: 6 janvier 2010 17:38:37 HNEC >>>>> >>>>> To: jboss-development(a)lists.jboss.org >>>>> >>>>> Subject: Re: [jboss-dev] Further profling: Where should I focus? >>>>> >>>>> Reply-To: "JBoss.org development list" >>>>> <jboss-development(a)lists.jboss.org&gt; >>>>> >>>>>> >>>>>> >>>>>> Any ETA on VFS3 being done and integrated with AS 6? >>>>>> >>>>> >>>>> My guesstimate is very early in the M3 cycle (i.e. as soon as we >>>>> open >>>>> trunk to commits after M2). So mid-February. >>>>> >>>>> It's tempting to try for M2, but there's only 3.5 weeks left before >>>>> component integration freeze, this is a big disruptive change and >>>>> there >>>>> are a couple issues to resolve: >>>>> >>>>> 1) Detecting modifications of exploded deployments: >>>>> http://community.jboss.org/thread/146098 >>>>> >>>>> 2) This caching discussion, which IMHO should continue. It's legit >>>>> to >>>>> think again about what the intended use cases are for VFS and see if >>>>> its >>>>> API can be adjusted to more effectively handle those use cases. >>>>> >>>>> The MC team is going to be putting out a 2.2 alpha release soon; >>>>> while >>>>> that's being integrated in the AS and issues resolved over the next >>>>> week >>>>> it makes little sense to try and start pushing in VFS3. So let's >>>>> use >>>>> that time to resolve the modification detection issue and discuss a >>>>> bit >>>>> more about caching. By the end of next week we should have a >>>>> clearer >>>>> picture as to whether trying for M2 is feasible. >>>>> >>>>> -- >>>>> Brian Stansberry >>>>> Lead, AS Clustering >>>>> JBoss by Red Hat >>>>> _______________________________________________ >>>>> jboss-development mailing list >>>>> jboss-development(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>>>> >>>> >>>> > >