As of this email's delivery time, I see only 4 builds [0] with failing tests, which are either new as a result of the migration to Red Deer 2.0, or intermittent failures. Except for the recurring failure, I have not yet opened JIRAs for these. I trust the project leads will do so. * central - maven.configurators * server - jmx.core * vpe - preview.editor * webservices - creation.core and jaxrs.core [1] This is OK for a milestone and won't block the build for QE spinning today/tonight (even if that jaxrs.core failure has been failing for over 20 builds!!). HOWEVER... There's also a bigger problem, which is that the integration-tests are not fully updated to run with Red Deer 2.0 [2]. As such these are still red and broken [3], and there will probably not be part of the content staged for QE [4] unless they're fixed before noon EST tomorrow. I don't consider this a blocker for the AM2 release, as they can be run (once fixed) as part of the QE review & signoff. [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [1] https://issues.jboss.org/browse/JBIDE-25017 [2] https://issues.jboss.org/browse/JBIDE-25013 and issues linked from https://issues.jboss.org/browse/JBIDE-24948 [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/jbosstools-i... [4] http://download.jboss.org/jbosstools/oxygen/staging/builds/ -- Nick Boldt Senior Software Engineer, RHCSA Productization Lead :: JBoss Tools & Dev Studio IM: @nickboldt / @nboldt / http://nick.divbyzero.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @ @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.facebook.com/RedHatInc>