Proposed 3.8.2 updates

Hi all,

attached a set of potential updates for 3.8.1 to move it to 3.8.2.

Included are
6748advance382a.cs
6750stringAndCharFixes-mir.cs (really a collection of fixes from 3.9/3.10)
6755SemaCritical-ar.cs
6754DelayStartup-ar.cs
6753DelayTweaks-ar.cs
6751SafeDelay-ar.cs
6752FreezeFix-ar.cs
6747advance381.cs
6749categoryspeedup-al.cs


Comments, suggestions for other fixes etc welcome!

Michael

Why don't you switch to 3.9 or 3.10?

2007/10/26, Michael Rueger <[hidden email]>:

--
Damien Cassou

Damien Cassou wrote:
> Why don't you switch to 3.9 or 3.10?

Reasons that have to do with reality outside universities:

1) a lot of people still use 3.8 so I continue to try to maintain it. I
think that is called support.

2) in projects with a tight schedule you usually don't have time to port
to the latest greatest, especially when your current version works just
fine.

Additional reason:
3) Sophie is stuck with Tweak which is stuck on 3.8

Michael

Because it can be a major effort (and risk) to move in case of larger  
applications.
Although we try to keep up to date, it sometimes does not make sense  
(for example if the system runs stable or if ressources are missing).  
We still use Squeak 3.7 in a couple of cases. Therefore, maintaining  
older versions is important.

Adrian

On Oct 26, 2007, at 15:24 , Damien Cassou wrote:

El 10/26/07 10:31 AM, "Michael Rueger" <[hidden email]> escribió:
You inspire me.
I have a 3.8.1 and wish port as mush is possible from 3.10 to 3.8.1 or any
future continuation you do.
Also I toying with shrink it same as 3.10 and use as base for experiments.

Continue good work and say if you need some help from me, via list or
private mail.

Edgar

Il giorno ven, 26/10/2007 alle 15.31 +0200, Michael Rueger ha scritto:
> Damien Cassou wrote:
> > Why don't you switch to 3.9 or 3.10?
>
> Reasons that have to do with reality outside universities:
>
> 1) a lot of people still use 3.8 so I continue to try to maintain it. I
> think that is called support.

Speaking of support, maybe it's time for the community to estabilish a
proper protocol for support. With this I mean what should happen to the
older versions when a new Squeak version is released.

I propose we steal a page from the *BSD and Debian books and have three
supported versions at every time: a stable, a current and a development
one. When a new development version is complete, it becomes the new
current version, the current version becomes the new stable one and the
stable one becomes legacy. Stable and current versions are guarenteed to
receive bug fixes (the stable one should receive only fixes for security
and major bugs), while there's no such warranty for the legacy versions.

Applied to the current situation, this would mean that 3.8.x is the
stable version right now, 3.9 is the current version while 3.10 is the
development version. When version 3.10 is released, 3.9 will become the
stable version, 3.10 the current one and 3.11 (or 4.0?) the next
development one. 3.8 could continue receiving bug fixes, if there's
someone who decides to produce them.

What do you think? Could a system be put in place?

        Ciao,

                Giovanni

El 10/27/07 7:13 AM, "Giovanni Corriga" <[hidden email]> escribió:

> What do you think? Could a system be put in place?
>
> Ciao,
>
> Giovanni

+1

Edgar

Full Agree with Michale and Adrian.

Not ever is possible to follow the new releases. The main goal of my production projects is stability and I have it with 3.8.

Cheers and Thanks by the support.

Hi mike

are these changes from sophie?
Did you include some fixes from the OLPC on font fixes?
and other.

For 3.11 I would like to bring the idea that the changes from sophie  
and OLPC are bring in Squeak.

Stef

On 26 oct. 07, at 15:19, Michael Rueger wrote: