So today is a bad day for target-platforms: some changes were requested and applied after TP was released. We'll investigate whether those changes were actually necessary and if they are worth a TP respin.

But please, do anticipate required TP change! We cannot afford to change TP on the day of a code freeze, that's a risky operation that slows us down our reduce our ability to ship on time and increase the risk of respins for QA.
The date of target-platform releases are on the JBDS-Tech calendar. Make sure your requests get it on time.

Although many supposed urgent changes were applied to 4.40.0.Beta2-SNAPSHOT (and may issues created/revealed as a side effect), all that just shows that urgent changes in TP are not good at all.
So my plan/with is still to use 4.40.0.Beta2 if possible. Depending on the criticity of the issues those changes try to fix, we can think about building a 4.40.0.Beta3 TP for JBoss Tools 4.2.0.Beta2. But that clearly is a bad thing because it would make the code-freeze more complex (master currently testing against Beta3-SNAPSHOT whereas it will be branched and built against Beta2 or maybe Beta3, we don't know yet....))


On 05/22/2014 12:11 AM, Nick Boldt wrote: