Re: [jbosstools-dev] Beta2 update - almost there! (was Re: Approaching Code Freeze for Beta2 :: FINAL ORDERS, PLEASE!)

From: "Max Andersen" <manderse(a)redhat.com&gt; To: "Nick Boldt" <nboldt(a)redhat.com&gt; Cc: "jbds-pm-list" <jbds-pm-list(a)redhat.com&gt;, jbosstools-dev(a)lists.jboss.org, external-exadel-list(a)redhat.com Sent: Friday, March 23, 2012 5:27:06 PM Subject: Re: [jbosstools-dev] Beta2 update - almost there! (was Re: Approaching Code Freeze for Beta2 :: FINAL ORDERS, PLEASE!)

I've just got info that the forge runtime fixes contains a bug. Everything else can be verified on this beta2 build. I hope to get more info soon to hear how severe the bug is.

Sent from a mobile device

On 23/03/2012, at 19.23, Nick Boldt <nboldt(a)redhat.com&gt; wrote:

> JBT 3.3.0.Beta2 is out (see other email w/ links). > > JBDS 5.0.0.Beta2 is pending. We're #7 in the Jenkins queue for the > last > build job in our stack, which produces the JBDS top-level product > feature (the one that allows the JBDS product to be updated). > > http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.product/ >> =115 > > As you of course know, this means the Beta1 branch is now CLOSED > for any > new commits. Please don't push anything in there w/o attaching a > patch > to a JIRA AND getting PM approval. > > Have a good weekend, > > Nick > > On 03/22/2012 01:06 PM, Nick Boldt wrote: >> Note that predictably, I announce "we might be able to do it >> sooner" and >> an hour later I've taken two slaves offline due to OOM and "no >> locks >> available" problems. >> >> https://engineering.redhat.com/rt/Ticket/Display.html?id=147071 >> https://engineering.redhat.com/rt/Ticket/Display.html?id=147072 >> >> On the plus side, Openshift is already done, so now we just need >> Maven, >> Forge, and VPE. >> >> On 03/22/2012 11:54 AM, Max Rydahl Andersen wrote: >>> >>> VPE and Forge will be fixed. >>> >>> WS/JAX-RS and Hibernate is being looked at but I do not think >>> they >>> will be relevant for beta2 at this time. >>> >>> /max >>> >>> On Mar 22, 2012, at 4:50 PM, Nick Boldt wrote: >>> >>>> I see 6 open issues assigned to a Beta2 target. >>>> >>>> Are all these going to be fixed& committed today or tomorrow? If >>>> not, >>>> can the owners move them off to Beta3 target? Components include >>>> WS, >>>> Hibernate, VPE& Forge. >>>> >>>> https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQu... >>>> >>>> >>>> >>>> - or - >>>> >>>> https://issues.jboss.org/secure/IssueNavigator.jspa?mode=show&createN... >>>> >>>> --> then paste in this: >>>> >>>> project in (JBIDE, JBDS, TOOLSDOC) AND fixVersion in >>>> ('5.0.0.Beta2', >>>> '3.3.0.Beta2') and Status not in (Resolved,Closed) >>>> >>>> >>>> On 03/22/2012 11:36 AM, Nick Boldt wrote: >>>>> Based on recent commits in SVN, I see two builds left to run >>>>> for Beta2: >>>>> >>>>> * OpenShift, SVN r39770, build #66 in progress (waiting for a >>>>> slave) >>>>> * Maven, SVN r39676, build #81 in progress (waiting for a >>>>> slave) >>>>> >>>>> Other respins are done, including: AS, Examples, VPE, >>>>> Hibernate, >>>>> Central, and Runtime. >>>>> >>>>> After that, we need to run the 3 aggregate jobs for JBT and >>>>> JBDS. >>>>> >>>>> -- >>>>> >>>>> Does anyone else have anything pending for commit to the Beta1 >>>>> branch >>>>> for inclusion in the Beta2 bits? If not, I may be able to get >>>>> the build >>>>> out to QE sooner than previously planned. >>>>> >>>> >>>> -- >>>> Nick Boldt :: JBoss by Red Hat >>>> Productization Lead :: JBoss Tools& Dev Studio >>>> http://nick.divbyzero.com >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> >>> >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev