<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>I want to get to where I can write a plug-in for the VM, have the VM see it and use it, then build a release with it. (locally, of course)<br><br>One motivation is urrent issues with I recently posted on regarding <br> VNC client on squeak primitiive error <br> SSL tanking on WebClient <br> The bug on Squeak4.4 and 4.5 where modifying a comment and attempting to save it throws a system level exception.<br>These are all things I want to use for projects I am working on and I don't know how to fix them.<br><br>t<br><br><br><br><br><br><br><br><br><br><br><div id="1"><br>---- On Thu, 12 Sep 2013 13:21:53 -0700 <b>Frank Shearar <frank.shearar@gmail.com></b> wrote ---- <br></div><br><blockquote style="border-left: 1px solid #0000FF; padding-left: 6px; margin:0 0 0 5px">That's from quite a while ago! Yes, it worked out, and I ended up <br>volunteering/being volunteered to get 4.4 released. You can find the <br>notes for the current release cycle at <br><a href="http://wiki.squeak.org/squeak/6189" target="_blank">http://wiki.squeak.org/squeak/6189</a>. <br> <br>I'm certainly not _opposed_ to documenting the release process in the <br>HelpBrowser. Some parts of the release process are of necessity <br>outside the image, but that's OK. <br> <br>I'm a bit confused by the way you talk about the release process <br>though. It's not something people need to run, usually. <br> <br>frank <br> <br>On 12 September 2013 19:15, gettimothy <<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>> wrote: <br>> Awesome. <br>> <br>> Thank you. <br>> <br>> I did a google on the Squeak Release process and found a thread (by you) <br>> here: <a href="http://forum.world.st/Squeak-release-process-td4640158.html" target="_blank">http://forum.world.st/Squeak-release-process-td4640158.html</a> <br>> <br>> Did that ever come to fruition? Would a HelpBrowser entry be helpful? (I <br>> will write it if so, and the information is available) <br>> <br>> The goal, is that newbs like me can get the release environment running <br>> locally and mash around a bit without bothering the experts too much. <br>> <br>> thx. <br>> <br>> <br>> <br>> <br>> ---- On Thu, 12 Sep 2013 10:31:41 -0700 Frank <br>> Shearar<<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>> wrote ---- <br>> <br>> Right. That version's somewhere around 300 commits behind Trunk. After <br>> you update the image (open the Squeak menu in the docking bar at the <br>> top, on the far left), you will find only ReleaseBuilder. <br>> <br>> You always have local storage available, in the form of an <br>> MCCacheRepository pointing to the /your/image/path/package-cache/ <br>> directory. <br>> <br>> We really ought to push out a more up-to-date image, which requires me <br>> to finish finding out why the continuous integration update-image.st <br>> script is broken. <br>> <br>> frank <br>> <br>> On 12 September 2013 17:22, gettimothy <<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>> wrote: <br>>> Good news on the trunk! <br>>> <br>>> I am confused by what you mean by 'There is no ReleaseBuilderForXdotY'. <br>>> <br>>> I went here: <a href="http://ftp.squeak.org/trunk/" target="_blank">http://ftp.squeak.org/trunk/</a> <br>>> <br>>> Downloaded the .image and .change, then copied over an existing cogvm, <br>>> sources and stuff, fired up and browsing <br>>> ReleaseBuilder --> show hierarchy yields: <br>>> <br>>> ProtoObject #() <br>>> Object #() <br>>> Behavior #('superclass' 'methodDict' 'format') <br>>> ClassDescription #('instanceVariables' 'organization') <br>>> Class #('subclasses' 'name' 'classPool' 'sharedPools' <br>>> 'environment' 'category') <br>>> ProtoObject class #() <br>>> Object class #() <br>>> <br>>> ReleaseBuilder class #() <br>>> ReleaseBuilderDeveloper class #() <br>>> ReleaseBuilderFor3dot10 class #('current') <br>>> ReleaseBuilderFor3dot11 class #() <br>>> ReleaseBuilderFor4dot3 class #() <br>>> ReleaseBuilderFor4dot4 class #() <br>>> ReleaseBuilderFor4dot5 class #() <br>>> ReleaseBuilderNihongo class #() <br>>> ReleaseBuilderSqueakland class #() <br>>> <br>>> Since this is the 4.5 release series, I was poking around in the <br>>> ReleaseBuilderFor4.5 to see if I could solve the image issue for you guys. <br>>> ReleaseBuilderFor4dot5 class>>prepareNewBuild hung when it tried to put my <br>>> (ahem) work up on trunk. <br>>> <br>>> It was then, I thought I should modify <br>>> ReleaseBuilderFor4dot5>>releaseRepository to store my work locally. <br>>> <br>>> If people commonly do that, I would like to mirror that style to keep <br>>> things <br>>> consistent. <br>>> <br>>> <br>>> <br>>> <br>>> <br>>> <br>>> ---- On Thu, 12 Sep 2013 07:21:23 -0700 Frank <br>>> Shearar<<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>> wrote ---- <br>>> <br>>> On 12 September 2013 14:00, gettimothy <<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>> wrote: <br>>>> Is there a best-practice for fiddling with ReleaseBuilderForXdotY ? <br>>>> <br>>>> I downloaded the latest trunk image so I could look at the recent <br>>>> background <br>>>> image issue and, after running ReleaseBuilderFor4dot5 <br>>>> class>>prepareNewBuild <br>>>> discovered that it uses MCHttpRepository to upload to the <br>>>> source.squeak.org/trunk. <br>>>> <br>>>> I was going to play around with MCFileBasedRepository to save locally, <br>>>> but <br>>>> decided to ask the list first. <br>>>> <br>>>> Also, my apologies if I accidently clobbered /trunk <br>>> <br>>> There is no ReleaseBuilderForXdotY. There is only ReleaseBuilder. <br>>> (Imagine that in a voice from Ghostbusters.) <br>>> <br>>> You probably won't be able to clobber trunk. Or, if you did, it's an <br>>> administrator who's to blame, because only a few folk have commit <br>>> rights to Trunk. (Unlike Inbox, which is world-writable.) <br>>> <br>>> frank <br>>> <br>>> <br>>> <br>>> <br>>> <br>> <br>> <br>> <br>> <br>> <br> <br></blockquote><br></div></body></html>