<div dir="ltr">Hi Frank! I actually put this message out to lure you into this discussion. :) Because, I want to move on 4.5 and I knew you had _something_ out there, but couldn't remember all the details.<div><br></div>
<div>The issues I faced with needing to get a new image were:<div><br></div><div>- I had to research the mailing list to find out where to download it. An automated build server is great for doing continuous *testing* and reporting, but it seems like for end-user downloads we should have a copy available at the usual place (<a href="http://ftp.squeak.org">ftp.squeak.org</a>).</div>
<div>- When I downloaded the image from CI, updated, and ran the tests, I found there were more tests failing than in another image that was simply updated from 4.4. Something seemed to be wrong with the image state.</div>
</div><div>- Since I was not really certain what all was done in that image, I could not trust putting it on the <a href="http://squeak.org">squeak.org</a> FTP site. The only way I could be SURE enough about the state of an image put there was to take the archive release image (4.4) and simply update it myself and save it.</div>
<div><br></div><div>So, the overarching requirements:</div><div><br></div><div> - Downloadable from <a href="http://squeak.org">squeak.org</a> domains.</div><div> - A way to know exactly how it was built: This means knowing which prior _full release image_ was started with, and what changes (both code and objects) were made.</div>
<div> - Reproducible build. My idea since 4.2 was to have a utility method on ReleaseBuilder do all of this so it would be visible straight in the trunk repository. I guess I always thought of the CI's responsibility as a on-going "test-status reporting" mechanism more than a deployment tool.</div>
<div><br></div><div> - Chris</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Dec 14, 2013 at 2:24 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's great for easing David's pain - something well worth doing<br>
(especially since I'm almost certainly a large contributing factor) -<br>
but as a general rule, if we can't use the automated builds to do<br>
this, I need to know, so I can fix it. Because we should, in a later<br>
version than 4.4, be producing and publishing artifacts in a<br>
completely automated fashion. We're not _quite_ there yet, but I need<br>
to know any shortcomings in the process if we're ever to reach that<br>
happy day.<br>
<span class="HOEnZb"><font color="#888888"><br>
frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 14 December 2013 20:21, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> The alpha image is nothing more than an updated 4.4 image (clicking through<br>
> all the merge requests), trimming MC cache, save image, done.<br>
><br>
><br>
> On Sat, Dec 14, 2013 at 2:20 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
>><br>
>> Dave just FYI I recently posted a new alpha image at<br>
>> <a href="http://ftp.squeak.org/4.5-alpha" target="_blank">http://ftp.squeak.org/4.5-alpha</a>. Filelist works there and it is currently<br>
>> basis for moving toward a release.<br>
>><br>
>><br>
>> On Sat, Dec 14, 2013 at 8:23 AM, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>><br>
>> wrote:<br>
>>><br>
>>> On Fri, Dec 13, 2013 at 05:05:27PM -0800, tim Rowledge wrote:<br>
>>> ><br>
>>> > On 13-12-2013, at 4:50 PM, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>>> ><br>
>>> > > I cannot open a file list (world -> open... -> file list) in a fully<br>
>>> > > updated trunk image.<br>
>>> > ><br>
>>> > > Is it just me?<br>
>>> ><br>
>>> > Possibly; my latest was -297 which worked ok and I just updated to 321<br>
>>> > and opening the filelist works ok. OS X 10.9, iMac, Cog vm. Only thing I<br>
>>> > noticed was a merge dialog popping up relating to some ST80 packages stuff.<br>
>>> ><br>
>>><br>
>>> It is indeed my image. I took another much older image and updated it<br>
>>> fully<br>
>>> to trunk, and the file list works fine.<br>
>>><br>
>>> Sorry for the noise.<br>
>>><br>
>>> Dave<br>
>>><br>
>>><br>
>><br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div></div>