<div dir="ltr">Hi Tobias,<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 12, 2015 at 12:49 PM, Tobias Pape <span dir="ltr"><<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 12.08.2015, at 20:55, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
<br>
> Hi All,<br>
><br>
><br>
> Fabio's kindly done most of the changes. But some questions remain for more general discussion. See below.<br>
><br>
> Fabio, thanks so much for doing this, and so quickly!<br>
><br>
> On Tue, Aug 11, 2015 at 8:51 PM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
> Hi All,<br>
><br>
> who will update <a href="http://squeak.org/downloads/" rel="noreferrer" target="_blank">http://squeak.org/downloads/</a> to include the 5.0 release?<br>
><br>
> a) I suggest that the 5.0 all-in-one have a line in the left-hand table that includes the 4.6 release and that it precede the 4.6 release in the list.<br>
><br>
> Done.<br>
><br>
><br>
> b) the Trunk link points to TrunkImage.zip which contains a non-Spur image.<br>
><br>
> So this is the biggie. What should we do?<br>
><br>
> - add a Trunk 5.0 build with a different link? (Noooooo)<br>
><br>
> - change <a href="http://build.squeak.org/job/SqueakTrunk" rel="noreferrer" target="_blank">http://build.squeak.org/job/SqueakTrunk</a> to build what it says (Yessss please, who can do this?)<br>
<br>
</span>Done: <a href="http://build.squeak.org/job/Trunk/" rel="noreferrer" target="_blank">build.squeak.org/job/Trunk/</a><br>
But as I said several times, Spur/trunk test just crash for month…<br></blockquote><div><br></div><div>can you point me to the crash? I'm looking at <a href="http://build.squeak.org/job/Trunk/default/lastBuild/#showFailuresLink">http://build.squeak.org/job/Trunk/default/lastBuild/#showFailuresLink</a> and see 8 test failures but no crash. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> - add a Squeak 4.6 build job? Is that even worth it any more considering 4.6 is released and stable? If it is then what should it build? David?<br>
><br>
><br>
> c) Spur VMs need to be linked to by an added line in the Virtual Machines list.<br>
><br>
> Not applicable. the VM links point to the root of my site so they effectively point to both old and Spur VMs.<br>
><br>
><br>
> d) Spur imagers need to be included in the Image and Changes list under Custom Installation<br>
><br>
> Done.<br>
><br>
><br>
><br>
> e) The SqueakV50.sources file also needs to be included in the Current Sources list.<br>
><br>
> Done.<br>
><br>
><br>
> f) we could start a History list for the 5.0 line<br>
><br>
> This is probably quite a big reorg on the page and not urgent.<br>
><br>
><br>
> So there are a few things to fix before 5.0 is freely downloadable.<br>
><br>
> On Tue, Aug 11, 2015 at 8:23 PM, Chris Muller <<a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a>> wrote:<br>
> In the 17 months since Squeak 4.5 was released, a huge development<br>
> effort took place to create the next generation virtual-machine for<br>
> the Squeak / Pharo / Newspeak family of programming systems. Squeak<br>
> is the modern incarnation of the Smalltalk-80 programming environment<br>
> originally developed at the Xerox PARC.<br>
><br>
> "Squeak 5" introduces this new VM and associated new memory model,<br>
> collectively referred to as "Spur". Presented [1] by Eliot Miranda<br>
> and Clément Béra at the 2015 International Symposium on Memory<br>
> Management, this new VM affords Squeak applications a significant<br>
> boost in performance and memory management. Among other<br>
> optimizations, the #become operation no longer requires a memory scan.<br>
> Object pinning and ephemerons are also now supported. The release<br>
> notes [2] provide more details.<br>
><br>
> The new memory model requires a new image file format. Although this<br>
> new format results in about a 15% increased memory requirement for the<br>
> same number of 4.x objects, a new segmented heap allows memory to be<br>
> given back to the OS when its no longer needed, a great benefit for<br>
> application servers.<br>
><br>
> As forward compatibility is as important to the Squeak community as<br>
> backward compatibility, Squeak 5 is delivers an image with identical<br>
> content as the recent 4.6 release. Although this new Squeak 5 VM<br>
> cannot open images saved under the prior 4.x Cog format, objects and<br>
> code can be easily exported from the 4.x image and then imported into<br>
> Squeak 5. Applications whose code runs strictly above the Smalltalk<br>
> meta layer will prove remarkably compatible with the new format, most<br>
> applications will require no changes whatsotever.<br>
><br>
> Squeak 5 is the result of monumental effort by a tiny group of very<br>
> talented people, but its also just the beginning of yet a new effort;<br>
> Spur is just a stepping stone to a more ambitious goals planned over<br>
> the next five years.<br>
><br>
> [1] -- A Partial Read Barrier for Efficient Support of Live<br>
> Object-oriented Programming<br>
> <a href="http://conf.researchr.org/event/ismm-2015/ismm-2015-papers-a-partial-read-barrier-for-efficient-support-of-live-object-oriented-programming" rel="noreferrer" target="_blank">http://conf.researchr.org/event/ismm-2015/ismm-2015-papers-a-partial-read-barrier-for-efficient-support-of-live-object-oriented-programming</a><br>
><br>
> [2] -- Squeak 5 Release Notes<br>
> <a href="http://wiki.squeak.org/squeak/6207" rel="noreferrer" target="_blank">http://wiki.squeak.org/squeak/6207</a><br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>