It was complete a long time ago, I was just preoccupied with a bad bug and 
forgot to announce. 

Thanks, 


P.S. For once I agree with Mickael. A failed build is not "bad" in cases 
like we saw with EGit's qualifier being wrong -- if for no other reason 
than we don't know if the qualifier was wrong. Perhaps something is wrong 
with their deployment or build, and a "loose" requirement would have made 
them miss that fact. Whereas now they have to investigate and explain 
themselves. :) Well, I hope they do! The only mistake they made was 
hitting "commit" and not waiting around to see what happened (perhaps 
because BIRT or others broke the build? (just a possible example -- I am 
guessing) and they could not wait around for BIRT to fix the build? Could 
be many reasons why, and I don't blame any one team as much as I sometimes 
sound, because we should all be acting like "one team - one product" when 
it comes to the Sim. Release! 

To "do a build" is easy. To do a build correctly is hard. 



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to