Re: [jbosstools-dev] Approaching Code Freeze for Beta2 :: FINAL ORDERS, PLEASE!
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