Release

release@lists.squeakfoundation.org

59 discussions

Start a nNew thread

[Fwd: Problem with installing DS on 3.10-lpf-atomic]
by Keith Hodges 03 Jul '09

03 Jul '09

1 1

Diary
by Keith Hodges 30 Jun '09

30 Jun '09

Fixed Bob to run from squeak.safeprayer.com - the only domain I currently own. Ran bob again results are builds stamped 090628-1523 The filesystem is visible at ftp://squeak@squeak.safeprayer.com/bob/ Results are available at ftp://squeak@squeak.safeprayer.com/bob/release or a few minutes later at http://ftp.squeak.org/3.11/ Updated InstallerScripts to use Monticello.impl.643 Attempted to fix Monticello15 in universes. Dug out IShowU to make some doc/screencasts My first attempt at a screen cast is available from: ftp://squeak:viewpoints@squeak.safeprayer.com/bob/docs Keith

2 3

Re: Pier-EmailSender and "Contact Us"
by Andreas Raab 05 May '09

05 May '09

Yes, good point. I've put it on the agenda for the board meeting: http://squeakboard.wordpress.com/2009/04/22/initial-agenda-for-may-7th-2009/ Cheers, - Andreas John M McIntosh wrote: > I note if you go to the squeak.org website and tap but report it dumps > you into Mantis. However for novices that likely isn't helpful > and the link to a mail message from Feb isn't something anyone is going > to find, or mmm or remember. > > On 5-May-09, at 9:05 AM, Andreas Raab wrote: > >> I'll check it out. Also note that cc-ing >> release(a)lists.squeakfoundation.org will generally be useful. >> >> Cheers, >> - Andreas >> >> John M McIntosh wrote: >>> Well then for http://bugs.squeak.org/view.php?id=6581 >>> who would stick that into 3.11? Let alone that I'm looking at 3.10.2 >>> image >>> Added (partly) >>> http://bugs.squeak.org/view.php?id=7348 >>> On 5-May-09, at 2:07 AM, Andreas Raab wrote: >>>> Hi John - >>>> >>>> John M McIntosh wrote: >>>>> (I had to fix the sq 3.10.2 image because of ignored bug using >>>>> allInstances I reported years back, never fixed, but fixed in pharo >>>>> last fall). >>>> >>>> [... snip ...] >>>> >>>>> (to be fair here I could bring some fixes into the 3.10.2 image to >>>>> reduce the cpu time, but really those fixes should have gone in >>>>> years ago...) >>>> >>>> Just as an FYI, there is now a well-defined process for contributing >>>> stuff to 3.11: >>>> >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095… >>>> >>>> >>>> If these fixes are on Mantis all you need is to provide an installer >>>> script and update its status accordingly. Just try it! >>>> >>>> Cheers, >>>> - Andreas > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

1 0

Re: Pier-EmailSender and "Contact Us"
by Andreas Raab 05 May '09

05 May '09

I'll check it out. Also note that cc-ing release(a)lists.squeakfoundation.org will generally be useful. Cheers, - Andreas John M McIntosh wrote: > Well then for http://bugs.squeak.org/view.php?id=6581 > who would stick that into 3.11? Let alone that I'm looking at 3.10.2 image > > > Added (partly) > http://bugs.squeak.org/view.php?id=7348 > > On 5-May-09, at 2:07 AM, Andreas Raab wrote: > >> Hi John - >> >> John M McIntosh wrote: >>> (I had to fix the sq 3.10.2 image because of ignored bug using >>> allInstances I reported years back, never fixed, but fixed in pharo >>> last fall). >> >> [... snip ...] >> >>> (to be fair here I could bring some fixes into the 3.10.2 image to >>> reduce the cpu time, but really those fixes should have gone in years >>> ago...) >> >> Just as an FYI, there is now a well-defined process for contributing >> stuff to 3.11: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134095… >> >> >> If these fixes are on Mantis all you need is to provide an installer >> script and update its status accordingly. Just try it! >> >> Cheers, >> - Andreas > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

1 0

Some more questions
by Andreas Raab 10 Apr '09

10 Apr '09

Hi - Being the new liaison and such I've done some more reading and I'm having a couple of questions trying to understand how the release team works. First off, who exactly is the release team? Can I ask the member of the release team to send a quick ping to show that they are present and able to communicate? ;-) Second, I'm still trying to figure out where we're going in 3.11. I have not yet seen much of a goal and I'm still very much unclear on where we are. I'm not asking Keith specifically, I'm asking *every* member of the release team to communicate their expectations about when 3.11 is to be considered done. This will either tell me that there is a good internal understanding of what 3.11 constitutes and help me sharing this understanding or it'll show that I'm not the only one who is confused about where we stand and where we're going. Either way it will be helpful. Lastly, I was flabbergasted when I looked at http://ftp.squeak.org/3.11/ I expected to find 3.11 versions but instead I find every Squeak version under the sun *except* 3.11. Does anyone know what these versions have to do with 3.11 and why they should be in the 3.11 directory? Is this just a mistake or is there reasoning behind that structure? Thanks for any info, - Andreas

2 2

Integrating an Installer wiki pages with squeak.org hosting
by Igor Stasenko 24 Mar '09

24 Mar '09

Keith, Ken, Matthew and Janko, i'd like to ask, if there are easy & fast solution to move installer scripts under our domain/hosting, to be not dependent from pbwiki. Janko, what you think how it could be easy/hard to enable Aida to support it? Ken, is there a technical possibility for doing this? If there is no big barriers, i'd like to put it to board discussion, and make a decision about it. I think it would be good to have everything under our control, since Installer is a core part of 3.11 release. Of course, if it is still relevant. -- Best regards, Igor Stasenko AKA sig.

3 2

[PRJ] Rio Http support
by Keith Hodges 27 Feb '09

27 Feb '09

A really simple project - fill in the HTTP support for Rio Keith

1 0

Installer-Formats pkg includes MczInstaller, SARInstaller
by Keith Hodges 24 Feb '09

24 Feb '09

I started a new package Installer-Formats, and put MczInstaller and SARInstaller in there. I think this makes sense, it moves them into a maintained package external to the image and hence transcentent to Squeak/Pharo. They are now included in LPF enabling any improvements to be distributed. It also makes the chaotic System category in the image two classes lighter. Keith

1 0

[PRJ] -fun
by Keith Hodges 23 Feb '09

23 Feb '09

I propose to list projects here that people could volunteer for, as a contribution to the 3.11 effort. Title: -fun images Description: Review edgar's fun image, and look to reproduce it via Sake/Packages package definitions. So that it may be loaded via. Installer sake install: 'Squeak-fun image'. Usefulness/Purpose: The same process will load into 3.11, and will provide a fuller image for test purposes, as well as providing users with a grand tour of what squeak can do. - Keith

1 0

[Ann] Bob is building
by Keith Hodges 23 Feb '09

23 Feb '09

Dear All, Bob is taking shape, he can now build images, package and upload the results. I have not yet posted this to squeak-dev, because I havent got time to handle a flood of enquireys just yet. Would anyone be willing to see if they can write the code to generate one click images? cheers Keith ==================== Public Bob Server Bob is now running at bob.warwick.st where he has 160Gb of space available for building in. His work is visible via http://bob.warwick.st and ftp://squeak@bob.warwick.st (password is the same as the swiki). At present it is necessary to be able to see what Bob is doing because Bob is not clever enough to spot or terminate builds that get stuck. (An OSProcess waitForCommand:withTimeout: would be useful). Secondly it is useful to debug as builds progress by enabling the stepping option. Thirdly some builds are not YET entirely unattended (e.g. squeak-dev). To make this possible there is a vnc server running which allows remote monitoring of Bob and the images which it launches. VNC is running on display 1 (port 5901) password is the same as the squeak swiki (for now). Bob can monitor squeaksource repositories rss feed and keep up to date with changes in Monticello repositories, currently: 1) "Packages" - where the published packages, and dependencies are maintained. 2) "Bob" - where build tasks, and build definitions are maintained. 3) He also monitors "Mantis" for changes every 15 minutes. Every 3 Minutes, he runs all the build tasks. Each of the build tasks checks to see if any of their input images have changed. Input images are usually in the form of a zip file as uploaded to the final destination server (ftp.squeak.org) This design, allows multiple Bob instances to run collaboratively in a distributed fashion. Each Bob selects which builds it wants to make, and whether or not it is responsible for doing the final upload. Thus the Bob instances co-orperate, using the "creationTime" on the zip files as a build triggering signal, as one uploads its completed build zip, another downloads that zip for its own tasks. Installing Bob ========== Bob will be a downloadable image, built by himself! Bob - Repositories/Packages ==================== Rio/File-Kernel Rio/File-Base - provides file handling Logging/Logging - provides logging front end Logging/SimpleLog - provides logging back end Sake/Sake - provides tasks and dependencies between builds Sake/Sake-Scheduler - periodic task execution Packages/Packages-Library - all the current package dependency definitions Sake/Sake-Bob - the top level bob tasks Bob/Bob-Releases - user defined build tasks for official releases Bob/Bob-SomeProduct - user defined bob build tasks for your own products (public) YourRepo/Bob-YourBuilds - user defined bob build tasks for your own products (private - run bob yourself). Bob - Server Configuration =================== All local configuration is done in class BobConfig, so if you are running your own Bob build/test server you can save and load all local settings as a class file out of BobConfig. examples: BobConfig class >> #configBaseDir ^ '/bob' asDirectory BobConfig class >> #configVm "the mac vm doesnt like to be opened via a symbolic link" ^ '/bob/vm/Squeak\ 3.8.20beta1U.app/Contents/MacOS/Squeak\ VM\ Opt' etc etc etc.... Bob - Build Customization =================== Your image builds will be defined as subclasses of BobBuildImage, and can be packaged and managed in the squeaksource/Bob repository. If a Bob server instance is aware of your package, then he may do your building for you. He will watch the Bob repository rss feed for changes, and will respond accordingly. Defining a Build a) Metadata b) build script ================================= Each build has a series of meta data methods, one per build number, e.g: build0000 info name: 'Squeak3.10.2-build'. info when: '2009-02-21T00:19:28.182+00:00'. info by: 'kph'. info image: 'ftp://ftp.squeak.org/3.10/Squeak3.10.2*basic.zip'. info stepping: true. info release: false. info upload: 'ssh://updates@squeakfoundation.org/var/www/files/3.11/3.10.2-build/'. info comment: 'testing'. "The code that follows is the central part of the script that is used to build the image" """""" Installer install: 'Tasks'. """""" "self halt." Squeak310MakeBuildCandidate taskBuild run. The above method defines metadata which tells bob, what the build is called, when to run it, where to obtain the starting image, whether to put "self halts" in at convenient places for debugging, and where to upload the results. When To Build - info when: ===================== code in #isBuildNeeded articulates rules which allow you to. 1) Build once at a specific time. 2) Build if a specific file (specified as a url with wildcards accepted) has changed. 3) Build if the starting image zip file (specified as a url with wildcards accepted) has changed. 4) Build periodically every x, minutes/days. 5) Build with a new explicit build number change 6) Do not build. The rules are evaluated as follows: a) If the output directory does not exist do not build (6) *** b) If "info when" = false or #dont then do not build. (6) c) If "info when" is a time that is not up yet then do not build. (1) d) If "info when" is a file match whose file is not found then do not build. (2) e) If "info image" zip file match is not found then do not build. (3) f) If the "info when" is a file match has changed since he last build, then a new build is needed. (2) g) If the "info image" zip has changed since he last build, then a new build is needed. (3) h) If the build number has changed a new build is needed. (5) i) If "info when" is a duration, build if the given time has passed since the previous build. (4) j) When "info when" is a time, if the previous build is the same or more modern do not build (1) If you run your own bob server he will attempt to build ALL of the defined tasks EVERY 3 minutes or so. So your primary way for indicating which of the builds you want is to create the output directory (option a) marked *** above. What To Build - #theScript ==================== theScript script reset. self scriptTranscriptLogToFileLoad; scriptTranscriptLogToFileStart; scriptAddLPF; scriptAddInfoScript; scriptTranscriptLogToFileStop; scriptSaveImageAndQuit: true The script is assembled using pre-prepared chunks like those above. You can define #theScript for your builds. #scriptAddInfoScript, incorporates the script elements that are appended to the metadata method. The script that this generates is written out and fed as an input to the chosen image. e,g. "self halt." HTTPSocket httpFileIn: 'installer.pbwiki.com/f/TranscriptToFile.cs'. !"self halt." Preferences setPreference: #logTranscriptToFile toValue: true. !"self halt." HTTPSocket httpFileIn: 'installer.pbwiki.com/f/LPF.st'. ! Installer install: 'Tasks'. ! Squeak310MakeBuildCandidate taskBuild run. !"self halt." Preferences setPreference: #logTranscriptToFile toValue: false. ! | image resuming | "self halt." SystemVersion newVersion: 'Squeak3.10.2-build'. SystemVersion current date: '2009-02-21T02:03:58.358+00:00' asDateAndTime. image := SmalltalkImage current. image cleanUpAllExcept: #(ChangeSet). resuming := image saveAs: '090221-0203_Squeak3.10.2-build.image'. resuming ifFalse: [ image snapshot: false andQuit: true ]. ! Note that when you write these script snippets they are expected to have "self halt." in them at strategic points. If the "info stepping" flag is set to true then these are uncommented. What To Build - Build order #dependsOn: ============================== The tasks are run in an order which suits all of the dependencies explicitly stated. self dependsOn: { BobBuild310Build build } Manually Running the build: ===================== [ BobBuild taskBuildAll run ] fork. and if immediate uploading is turned off, #configUploadImmediately, a manual upload can be performed later via. BobBuild310Dev upload run.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Release