<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">Two points<br class=""><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><br class=""></div></div></div><div class="">You know that I'm not found of the break it first, fix it later strategy.<br class=""></div></div></div></div></div></div></div></blockquote><div class=""><br class=""></div>I have no problem with that.</div><div class="">I have problem that automated tests do not catch it to free programmers and brain. </div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Though it sometimes happen that I get caught.<br class=""></div><div class="">Here it sounds like you are not granting to me this right to break things when in the same time this right is totally abused in every day Pharo development…</div></div></div></div></div></div></div></blockquote><div class=""><br class=""></div>You see in Pharo our process is stagged. If the tests to not run, the tests is not in. </div><div class="">For example this year we did not integrate Epicea and marcus tried 15 times (for real 15 times) </div><div class="">this is just that you did not see it. Now we break things because we do not have enough tests and UI/widgets is not covered. </div><div class=""><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">So despite the fact that you are completely right this time, I'd say that I would have been more inclined to take the lesson I deserved from say Eliot ;)<br class=""></div></div></div></div><br class=""></div>I'm taking too much time writing this when there's probably more trouble with the spur VM currently and that ain't good.<br class=""></div><div class="">Stephane, I like your energy, and I wish I could use and promote Pharo, but please, keep it positive :)<br class=""></div><div class="">Tonight, you gave me bad vibrations :(<br class=""><br class=""></div><div class="">Nicolas<br class=""></div><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2016-03-18 22:13 GMT+01:00 stephane ducasse <span dir="ltr" class=""><<a href="mailto:stephane.ducasse@gmail.com" target="_blank" class="">stephane.ducasse@gmail.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><br class="">I wonder why you do not check our builds before pushing a change. Staging changes can make sure that<br class="">we control the propagation of errors. And as you know, error = time = money.<br class="">This is always difficult for someone to try to understand error that he had no clue from where they come.<br class=""><br class="">Stef</blockquote></div><br class=""></div></blockquote></div><br class=""><div apple-content-edited="true" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><br class=""></div></div></div></div></div></body></html>