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

On Tue, Mar 26, 2013 at 11:53:36PM -0400, Nick Boldt wrote: > 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. What went wrong is that Alexey believed the jobs were disabled so they would not get in - but yes, I agree it was premature to put them in. > 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. It is in there now. If QE do not want it we will have to revert;but lets see what QE sees/finds before spending more time back and forth. But from now - 4.0.x is *frozen solid*. /max > 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(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)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