Release December 2008

release@lists.squeakfoundation.org

4 participants
7 discussions

Re: The progress status on V4?
by Matthew Fulmer 18 Dec '08

18 Dec '08

On Wed, Dec 17, 2008 at 11:16:13AM -0800, Yoshiki Ohshima wrote: > Hello, > > How are you guys doing? This is a bi-weekly query of the progress > on it. Apparently, the other kinds of work toward the new release is > taking shape, but just a formality, I'd ask it. I have done no work on the relicense work since last meeting, and I probably won't be able to for at least two weeks, as I am in the final stages of getting ready to move across the country. If you could, please direct all further inquiries to our mailing list, release(a)lists.squeakfoundation.org -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

2 1

First Build
by Keith Hodges 15 Dec '08

15 Dec '08

Greetings all! I have put a first build image, 081214-0249-Squeak3.10.2bc-beta, on the ftp site This is the 3.10.2 Build Candidate, intended to be the "preferred" 3.10 based image on which to apply image building scripts. I would welcome any feedback: There are still couple of ideas for inclusion prior to final. 1. Don't throw away bug fix change sets in SmalltalkImage current cleanUpAll. 2. Name ChangesSets with the bug fix number as a prefix. 3. Test Unloading of all extra packages. 4. Tidy the existing tasks and list some road map idea-tasks for the future. best regards Keith

1 0

Mantis automation
by Keith Hodges 11 Dec '08

11 Dec '08

Hi Ken, Matthew, Igor, I am looking at automating more of our use of mantis. I think it would be nice if we could run code like that below: (assuming that no changes have been made to mantis so far) ========= Installer mantis select: [ :ea | ea isStatusConfirmed ] thenDo: [ :ea | ea ensureFix ]. self isUnstable ifTrue: [ Installer mantis select: [ :ea | ea isStatusAcknowledged ] thenDo: [ :ea | ea ensureFix ] ]. (the actual code will be more complex, because we will want to pay attention to dependencies) ========= What I would like to see is the summary view colours indicating exactly what will happen to the fix. Colours/Levels desired are: 1 A fix script is available (assigned / fix-script-available) 2 fix is included in the unstable build (acknowledged / unstable) 3 fix is included in the stable build (confirmed / stable) 4 fix is in a release (resolved) One problem with this idea is that if you want to request discussion on a fix then moving it to "feedback" will pull it out of the build, (perhaps that is not a bad thing) Item 1, on the list didn't seem to be important enough to require a colour of its own. Furthermore I felt it would be good to have some way for the writer of the fix to indicate his level of confidence in the fix. i.e. "I think this should go in to the stable build", I thought that we could use the resolved field for this. i.e "open" "fix available" "fix needs testing" "fix is good to go" "fix is deployed" i.e. "fixed". Another possibility, which is perhaps easier to use is to have "special users" Assign to user "Rel-inbox" - fix available Assign to user "Rel-testing" - fix is suitable for the unstable build Assign to user "Rel-outbox" - fix should be in the stable build. hopefully that's a bit clearer so given that the special users idea gives me the extra features that I want, shall we go with this. However it might be useful to put a explanation on the front page. thanks Keith

2 1

[Bug] Installer mantis .cs.gz files
by Keith Hodges 09 Dec '08

09 Dec '08

Installer mantis bug: 6843 fix: 'FixSMTPAuthEncoding.1.cs.gz'. not working Keith

1 0

Re: [squeak-dev] Forking
by Keith Hodges 08 Dec '08

08 Dec '08

> I am most curious about what will happen to 3.10 when 3.11 is released. > > Thanks, > TimJ Here is the theory! In an LPF image: Installer install: 'Tasks'. The main workflow is summarized in the following releases generated by the following classes/tasks which need to be fleshed out. Squeak 3.11 Personal Test Candidate - ReleaseAfterSqueak310Kph-#taskTESTCANDIDATE. Squeak 3.11 Unstable T.C. - ReleaseAfterSqueak310Unstable-#taskTESTCANDIDATE. Squeak 3.11 Stable T.C. - ReleaseAfterSqueak310-#taskTESTCANDIDATE. Squeak 3.11-basic Release Candidate - ReleaseSqueak311-#taskRELEASECANDIDATE. Squeak 3.11-basic Golden - ReleaseSqueak311-#taskGoGolden. Derived images Squeak-3.x-dev - Packages current load: 'Squeak-dev image'. (czar: damien, should already work in 3.9+) Squeak-3.x-web - Packages current load: 'Squeak-web image'. (ditto) Squeak-3.x-devbeta - Packages beta load: 'Squeak-dev image'. (ditto) Squeak-3.x-webbeta - Packages beta load: 'Squeak-web image'. (ditto) Squeak-3.x-fullbeta - Packages beta load: 'Squeak-full image'. (czar wanted) Squeak-3.x-full - Packages current load: 'Squeak-full image'. Squeak-3.x-max - Packages current load: 'Squeak-max image'. (czar wanted) Squeak-3.x-fun - tba (czar wanted) Squeak-3.x(-*whatever*)-test - Packages current load: 'AllTests'. (loads tests into any image Squeak-3.x-seaside - Packages current load: 'Squeak-seaside image'. Squeak 3.x-(*whatever*)-oneclick - ReleaseX-taskGenerateOneClick. Squeak 3.11-minimal - Release311-#taskMINIMAL Squeak 3.11-kernel - Release311-#taskKERNEL Squeak 3.11.1-basic - Release311-#taskUPDATE1 Squeak 3.11.2-basic - Release311-#taskUPDATE2 So by extension, those who only want a minor update of the most essentially essential fixes to 3.10 there is a set of tasks managed by class ReleaseSqueak31-#taskUPDATE3 This would be applied via: Installer install: 'Tasks'. ReleaseSqueak310 taskUPDATE3103 run. Packages current unload: 'Sake'. (to remove all vestiges of the Sake/Tasks/Packages). cheers Keith

1 1

Re: The progress status on V4?
by Keith Hodges 02 Dec '08

02 Dec '08

Yoshiki, do join us on the release(a)lists.squeakfoundation.org list. Matthew Fulmer wrote: > On Mon, Dec 01, 2008 at 03:13:04PM -0800, Yoshiki Ohshima wrote: > >> Hi, Matthew and Keith, >> >> On behalf of the board, now I'm supposed to be checking with you >> guys about the status of the effort for making a relicensed Squeak >> V4 regularly. >> >> Craig told me that Keith (IIRC) won't have much time until sometime, >> but I got some messages from Matthew about the Authorship code... >> What should I say to the "leadership"? >> > > I worked on this three days last week. I started with your 3.10 > history image, made a file containing all the dirty methods, and > now I'm annotating it with every change you made to etoys, to > see what would still need relicensing after I applied your etoys > 3.2 changes, and whether they would apply cleanly. So far, I > have gone through about 4 of your 10 etoys changesets. > > My plan is something like this: > > - Check to see what yoshiki's changesets don't cover (40% done) > - Apply yoshiki's changesets to 3.10, carefully > How are you planning to publish the results? Would they be in a changeset/equivalent that is loadable as a 3.11 build task? > - Confirm and fix the licensing status of new modules in 3.10: > - Traits (almost certainly clean) > - Universes (probably clean) > - Monticello (yikes) > - Do whatever I missed above > Keith

2 1

3.11 status
by Keith Hodges 02 Dec '08

02 Dec '08

Hello All, just a update as to where we are. My personal life has got a whole lot better recently. No more visiting hospitals etc, so a bit more time for Squeaking. Although my commercial project is still a high priority, I have started to spend time at the weekends working on Squeak stuff that I can also use as part of my paid work. i.e. not everything is directly 3.11 related, but it does have a contribution to make. My thinking is still, that 3.11 is about getting tools working really well for squeak accross the board. The Pharo guys are doing some great work on the kernel, and we will be able to benefit from their work significantly in the longer term. So tools wise: MC1.6 (LevelPlayingField) ==================== The goal is to have a definitive supported Monticello for everyone who uses MC1 packages. We expect MC2 to take a while to come into regular use, but we don't expect MC1 to disappear any time soon. Matthew is making great progress with Traits support for MC1.6, and I have been using MC1.6 for my development images. It is really nice and fast. Sake/Packages ========== To prepare for smaller images, a good solution for loading things back in is needed. Building images (like the dev image) also needs a good solution. To make Sake/Packages even better I have developed an automatic 'beta' loading feature. If a package definition (from universes or elsewhere) supplies a url for loading a package from a repository supported by Installer (e.g. Installer squeaksource). Packages beta, will dissect that url and attempt to find the repository and the most recent version from that repository. Packages current load: 'Aida'. - will load the released version of AidaWeb and its dependencies (Swazoo). Packages beta load: 'Aida'. - will track down the most recent version of AidaWeb and Swazoo. Bob The Builder ============ Bob is very close to completion now that Rio has been updated and revised. Rio - File/Directory ============== Key to the workings of Bob. Rio File/Directory package has been revised, refactored massively, simplified greatly, some more tests and transparent FTP support has been added (the feature Bob was wiating on). Logging (Used by Sake and Bob) ======================== Big refactoring, simplification, and much more powerful configuration options available. I need this for my commercial project, where I want my different seaside users to generate separate logs of their activities on my website. best regards Keith

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Release December 2008