<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="">Hi, <div class=""><br class=""></div><div class="">Sorry for urging on this, but as I said, I need to start working in this… Fabio just told me that he is ready for the migration and this mails from Tim confirmes it… </div><div class="">Can we schedule the migration?</div><div class=""><br class=""></div><div class="">Let’s say some day next week? (Thursday, as Fabio suggested)?</div><div class=""><br class=""></div><div class="">Can we have a “good to go”?</div><div class=""><br class=""></div><div class="">thanks! </div><div class="">Esteban</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 07 Jun 2016, at 20:13, Tim Felgentreff <<a href="mailto:timfelgentreff@gmail.com" class="">timfelgentreff@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">Fabio and I have finished integrating the changes to move to Github with a minimal patch against the current Cog branch. All scripts and build files have been migrated and we are building VMs for Newspeak, Squeak, and Pharo in the available flavor combinations (stack, cog, sista, spur, v3) on (what we think are) the most important platforms (linux, mac, windows) and the most used architectures (x86, x86_64, ARM).</p><p dir="ltr" class="">The patch ist currently on <a href="http://github.com/timfel/squeakvm" class="">github.com/timfel/squeakvm</a> and can be rebased onto the current SVN easily. I have currently disabled uploading the build artifacts. I was thinking maybe we could still use Eliot's webspace or else Bintray, but whatever the community thinks works best. </p><p dir="ltr" class="">As soon as everyone is happy with it the patch, we need to find a time when we switch the SVN to read-only and I rebase the patch one last time and then we go live on OpenSmalltalk/vm</p><p dir="ltr" class="">Best,<br class="">
Tim<br class="">
</p>
<div class="gmail_quote">Am 03.06.2016 15:25 schrieb "Esteban Lorenzano" <<a href="mailto:estebanlm@gmail.com" class="">estebanlm@gmail.com</a>>:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br class=""><div style="word-wrap:break-word" class="">Hi, <div class=""><br class=""></div><div class="">Last week (with help of Clement) I put online the 64bits image generation for Pharo. </div><div class="">Our CI now is producing regularly 64bits for both: </div><div class=""><br class=""></div><div class="">- Pharo 5: <a href="https://ci.inria.fr/pharo/view/5.0/job/Pharo-5.0-Update-Step-3.1-64bits/" target="_blank" class="">https://ci.inria.fr/pharo/view/5.0/job/Pharo-5.0-Update-Step-3.1-64bits/</a></div><div class="">- Pharo 6: <a href="https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.1-64bits" target="_blank" class="">https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.1-64bits</a></div><div class=""><br class=""></div><div class="">Now… I would like to start testing it, and for that I need to build also PharoVM 64bits… I do not wan to reproduce all the work already done for running 64bits in current so I’m urging you to complete the migration, so I can start to merge my changes into the master, instead the opposite :)</div><div class=""><br class=""></div><div class="">cheers, </div><div class="">Esteban</div></div><br class=""></blockquote></div>
</div></blockquote></div><br class=""></div></body></html>