[jbosstools-dev] Fixes in loading jars in KB model

[Nick Boldt]

Regrettably, the jobs had already spun by the time I saw your comments 
here. Next time please disable jobs that should not be run AND announce 
the fact that commits in the branch should NOT be included in the build 
stack.

Note too that committing code to the 4.0.x branch BEFORE we release a 
.Final build means there's a good chance it will slip into a build, 
especially if I've turned on all the jobs to verify that everything can 
build correctly against a new TP (JBIDE-13603).

It's better to wait until after the 4.0.1.Final release if you want it 
to end up in a hypothetical unscheduled future 4.0.2 release.

N

On 03/26/2013 06:08 PM, Max Rydahl Andersen wrote:
> On Tue, Mar 26, 2013 at 04:34:45PM -0400, Max Rydahl Andersen wrote:
>>> Since, the fix is so trivial, it could be merged into 4.0.x. Is it ok
>>> to have it included into 4.0.1 version, or should it wait until 4.0.2?
>>
>> Does all test pass ? Did the fix have some great effect and have you pinged QE to do a test run ?
>>
>> Since 4.0.1 is to go out anytime soon I would probably wait to avoid any surprises.
>
> Slava, Alexey, Nick - just to repeat what was talked about on irc:
> talking through with dgolovin we say do *not* apply/include these for 4.0.1; its too close.
>
> only put it in 4.0.2.
>
> No more extra builds for 4.0.1
>
>> /max
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at 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