Had a problem w/ the aggregate & product builds in the new branch due to
configuration changes we've done since Beta2 not propagating to the
updated jobs. So... respinning. Should have something for QE in a few hours.
The impatient among you can begin preliminary testing from the staging
composite site, while you wait for an official build:
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3....
---//---
Note too there are a few test failures in the components built from the
new branch:
https://issues.jboss.org/browse/JBIDE-11716 (AS, new failure)
https://issues.jboss.org/browse/JBIDE-11717 (Central, intermittent failures)
There's also a forge issue assigned to Beta2 which is still unresolved:
https://issues.jboss.org/browse/JBIDE-11384
---//---
Open issues for Beta3 are available as a query here, currently sorted by
priority:
**
https://issues.jboss.org/secure/IssueNavigator.jspa?requestId=12317113 **
If you see your name on that list, and you won't have time to fix the
outstanding issue w/ a patch & approval from Max, PLEASE reassign the
issue to the CR1 target so it's no longer in the Beta3 list, and fix it
in trunk. THANKS!
On 04/30/2012 05:42 AM, Max Rydahl Andersen wrote:
> Note that we are *code frozen* for Beta3, which means only urgent
fixes
> should be done in the branch, associated w/ a JIRA.
w/a Jira + review by Denis, Alexey or me.
btw. an old but easy forgotten svn tip:
doing svn switch
http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.0.Beta3/
in a copy of trunk or i.e. your old checkout of Beta1
is much faster than a full svn checkout.
/max
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com