Hi Eliot,
I feel your pain. My I ask, what was your process for deciding that a VM is a stable one on http://www.mirandabanda.org/files/Cog/VM/ before the switch to GitHub? Could this old process be used on GitHub as well and if not, why not?
Thanks for your terrific work on the VMs!
Best, Bernhard
Am 27.05.2018 um 10:06 schrieb Eliot Miranda eliot.miranda@gmail.com:
Hi,
On May 26, 2018, at 2:02 PM, Fabio Niephaus lists@fniephaus.com wrote:
On Sat, May 26, 2018 at 6:40 PM Bernhard Pieber bernhard@pieber.com wrote: Hi,
So it was just race condition. :-)
Thank you for fixing the upload!
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 https://bintray.com/opensmalltalk/vm/cog).
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. 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.
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?!?!
Fabio
[1] https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/201804030952 [2] https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest
Should testing happen with this VM or with the latest from Bintray?
Cheers, Bernhard
Am 26.05.2018 um 16:58 schrieb Fabio Niephaus lists@fniephaus.com:
Dear all,
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]. Although recent TravisCI builds have passed, this folder was empty because of an issue with the updater which Marcel and I just resolved. Therefore, all new artifacts are now uploaded to the 5.2alpha directory and should show up at [1]/[2].
Happy testing!
Fabio
[1] http://files.squeak.org/trunk/ [2] http://files.squeak.org/5.2alpha/
On Sat, May 26, 2018 at 1:20 PM H. Hirzel hannes.hirzel@gmail.com wrote: Hi Bernard
A solution which works well for the meantime is to take early May download from
http://files.squeak.org/6.0alpha/
And update from within the image.
One of the updates is the rename to 5.2alpha. The result is attached.
Regards --Hannes
On 5/26/18, Bernhard Pieber bernhard@pieber.com wrote:
Hi,
I wanted to get a current trunk image to help testing the new release. Normally, I go to http://squeak.org/downloads/ and click the trunk link http://files.squeak.org/trunk/. This leads to an empty directory. I guess this might be an unintended consquence of the rename.
Are you going to rename the folder and files in http://files.squeak.org/6.0alpha/ as well?
Best, Bernhard
Am 24.05.2018 um 10:44 schrieb Marcel Taeumel Marcel.Taeumel@hpi.de:
Hi, there.
We are going to change the current version number of the Trunk to "5.2alpha" to denote our plans for the upcoming Squeak release. After several discussions within the board and with our release manager Edgar, we came to conclusion that it makes sense to postpone the "6.0" a little bit to finish some bigger concerns such as the use of ephemerons and Etoys clean-up.
Best, Marcel