<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Marcel,<br><br></div><div><br>On May 27, 2018, at 1:45 AM, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de">marcel.taeumel@hpi.de</a>> wrote:<br><br></div><blockquote type="cite"><div><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: Calibri;color: #000000">
Hi Eliot,<div><br></div><div>the latest pre-release seems okay. I have been using it for several weeks now. I suppose that the "last stable" from 2016 is not any different from our recent pre-release in terms of stability. Nothing changed with regard to some stability metrics in the last years. If it builds and lasts a few weeks, it should be fine. :-) Yet, the frequent seg-faults in the CI during test runs are kind of unsettling. :-/</div></div></div></blockquote><div><br></div>There have to be major differences in circumstances we do t have reliable tests for as a number of serious vm bugs have been fixed.<div><br></div><div>What I find depressing is that we don't have a process that promotes stable VMs to a Pam e where they are easily downloaded. People are still using the 2016 VMs. This is broken.</div><div><br><blockquote type="cite"><div><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: Calibri;color: #000000"><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 27.05.2018 10:07:01 schrieb Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>>:</p><div>Hi,</div><div><br>On May 26, 2018, at 2:02 PM, Fabio Niephaus <<a href="mailto:lists@fniephaus.com">lists@fniephaus.com</a>> wrote:<br><br></div><blockquote type="cite" style="min-width: 500px"><div><div dir="ltr"><br><br><br><div class="gmail_quote"><div dir="ltr">On Sat, May 26, 2018 at 6:40 PM Bernhard Pieber <<a href="mailto:bernhard@pieber.com">bernhard@pieber.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin: 0 0 0 .8ex;border-left: 1px #ccc solid;padding-left: 1ex;min-width: 500px">Hi,<br>
<br>
So it was just race condition. :-)<br>
<br>
Thank you for fixing the upload!<br>
<br>
I saw that the 5.2alpha build contains the VM with the version 201804030952, which is not the latest version on Bintray (and interestingly is not even in the versions list on <a href="https://bintray.com/opensmalltalk/vm/cog" rel="noreferrer" target="_blank">https://bintray.com/opensmalltalk/vm/cog</a>).<br></blockquote><div><br></div><div>The VMs on Bintray are removed after a few weeks to save storage costs. More importantly, these VMs are considered bleeding edge and I don't think it's a good idea to test a bleeding edge Squeak image with a bleeding edge VM. If something is broken, it can be really hard to tell if the problem is in the VM or in the image.</div><div>The VMs that ship with the current 5.2alpha builds are from the latest VM pre-release which you can find at [1]. Unfortunately, the latest stable VM release [2] is from 2016.</div></div></div></div></blockquote><div><br></div>This is so depressing. What's the process by which a stable VM release is made? That process is broken. We have to fix it. 2016?!?!<div><br><blockquote type="cite" style="min-width: 500px"><div dir="ltr"><div class="gmail_quote"><div>Fabio</div><div><br></div><div>[1] <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/201804030952">https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/201804030952</a></div><div>[2] <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest">https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest</a></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin: 0 0 0 .8ex;border-left: 1px #ccc solid;padding-left: 1ex;min-width: 500px">
<br>
Should testing happen with this VM or with the latest from Bintray?<br>
<br>
Cheers,<br>
Bernhard<br>
<br>
> Am 26.05.2018 um 16:58 schrieb Fabio Niephaus <<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>>:<br>
> <br>
> Dear all,<br>
> <br>
> TravisCI just generated the first set of 5.2alpha artifacts including updated VMs which are now available at [1]. This URL actually links to the same folder you can find at [2].<br>
> Although recent TravisCI builds have passed, this folder was empty because of an issue with the updater which Marcel and I just resolved.<br>
> Therefore, all new artifacts are now uploaded to the 5.2alpha directory and should show up at [1]/[2].<br>
> <br>
> Happy testing!<br>
> <br>
> Fabio<br>
> <br>
> [1] <a href="http://files.squeak.org/trunk/" rel="noreferrer" target="_blank">http://files.squeak.org/trunk/</a><br>
> [2] <a href="http://files.squeak.org/5.2alpha/" rel="noreferrer" target="_blank">http://files.squeak.org/5.2alpha/</a><br>
> <br>
> <br>
> On Sat, May 26, 2018 at 1:20 PM H. Hirzel <<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>> wrote:<br>
> Hi Bernard<br>
> <br>
> A solution which works well for the meantime is to take early May download from<br>
> <br>
> <a href="http://files.squeak.org/6.0alpha/" rel="noreferrer" target="_blank">http://files.squeak.org/6.0alpha/</a><br>
> <br>
> And update from within the image.<br>
> <br>
> One of the updates is the rename to 5.2alpha. The result is attached.<br>
> <br>
> Regards<br>
> --Hannes<br>
> <br>
> <br>
> <br>
> <br>
> On 5/26/18, Bernhard Pieber <<a href="mailto:bernhard@pieber.com" target="_blank">bernhard@pieber.com</a>> wrote:<br>
> > Hi,<br>
> ><br>
> > I wanted to get a current trunk image to help testing the new release.<br>
> > Normally, I go to <a href="http://squeak.org/downloads/" rel="noreferrer" target="_blank">http://squeak.org/downloads/</a> and click the trunk link<br>
> > <a href="http://files.squeak.org/trunk/" rel="noreferrer" target="_blank">http://files.squeak.org/trunk/</a>. This leads to an empty directory. I guess<br>
> > this might be an unintended consquence of the rename.<br>
> ><br>
> > Are you going to rename the folder and files in<br>
> > <a href="http://files.squeak.org/6.0alpha/" rel="noreferrer" target="_blank">http://files.squeak.org/6.0alpha/</a> as well?<br>
> ><br>
> > Best,<br>
> > Bernhard<br>
> ><br>
> >> Am 24.05.2018 um 10:44 schrieb Marcel Taeumel <<a href="mailto:Marcel.Taeumel@hpi.de" target="_blank">Marcel.Taeumel@hpi.de</a>>:<br>
> >><br>
> >> Hi, there.<br>
> >><br>
> >> We are going to change the current version number of the Trunk to<br>
> >> "5.2alpha" to denote our plans for the upcoming Squeak release. After<br>
> >> several discussions within the board and with our release manager Edgar,<br>
> >> we came to conclusion that it makes sense to postpone the "6.0" a little<br>
> >> bit to finish some bigger concerns such as the use of ephemerons and Etoys<br>
> >> clean-up.<br>
> >><br>
> >> Best,<br>
> >> Marcel<br></blockquote></div></div></blockquote></div>
</blockquote></div></div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></div></body></html>