To prepare 3.9.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

To prepare 3.9.1

stephane ducasse
Hi all

some people asked if we could produce 3.9.1.
Here is their list of suggested items:

"We use the following three fixes that are crucial for any server setup:
0006581: Image freezes (background processes like Seaside make no  
progress) and Squeak hoggs CPU
This is the image freezing problem, where connecting with VNC and  
moving the mouse would bring the image alive again. When being stuck,  
Squeak hoggs the CPU, memory consumtion is stable. http://bugs.squeak.org/view.php?id=6581
Note: fix takes only effect if Preferences enable: #serverMode !
--------
0006588: Broken Semaphore>>critical: leads to frozen processes in Delay
VNC doesn't respond to UI events, 0% cpu usage, several processes  
frozen in Delay although our Seaside server still responds. http://bugs.squeak.org/view.php?id=6588
--------
0006576: Delay is not thread-safe
Delay is not thread-safe since currently the calling process updates  
the internal Delay structure itself. If the process gets terminated  
while doing this (e.g., adding/removing from SuspendedDelays) the  
whole system is left in an inconsistent state and breaks. http://bugs.squeak.org/view.php?id=6576
--------
0006524: TTFonts can't load unicode character maps
- http://bugs.squeak.org/view.php?id=6524
--------
Font caching
http://bugs.squeak.org/view.php?id=6089

Something else, that would be good to change is to remove OmniBrowser.  
There are two reasons why I've done this manually for the base image  
of our build process:
- with the old version of OmniBrowser installed the newer version  
cannot be loaded automatically with Monticello (If I remember  
correctly because there packages have been moved or renamed)
- for production we need small images (a few MBs per image can make a  
significant difference when running hundreds of images)

Now tell me if some others are important for us.
I was thinking that Nebraska and Speech could be removed too.

So let me know I will try to do my best to produce 3.9.1

Stef


Reply | Threaded
Open this post in threaded view
|

RE: To prepare 3.9.1

Ramon Leon-5
>
> Hi all
>
> some people asked if we could produce 3.9.1.
> Here is their list of suggested items:
> Stef

Sounds great, please do!

Ramon Leon
http://onsmalltalk.com


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Philippe Marschall
In reply to this post by stephane ducasse
2008/2/1, stephane ducasse <[hidden email]>:
> Hi all
>
> some people asked if we could produce 3.9.1.

That would be really appreciated from my side.

> Here is their list of suggested items:
>
> "We use the following three fixes that are crucial for any server setup:
> 0006581: Image freezes (background processes like Seaside make no
> progress) and Squeak hoggs CPU
> This is the image freezing problem, where connecting with VNC and
> moving the mouse would bring the image alive again. When being stuck,
> Squeak hoggs the CPU, memory consumtion is stable. http://bugs.squeak.org/view.php?id=6581
> Note: fix takes only effect if Preferences enable: #serverMode !
> --------
> 0006588: Broken Semaphore>>critical: leads to frozen processes in Delay
> VNC doesn't respond to UI events, 0% cpu usage, several processes
> frozen in Delay although our Seaside server still responds. http://bugs.squeak.org/view.php?id=6588
> --------
> 0006576: Delay is not thread-safe
> Delay is not thread-safe since currently the calling process updates
> the internal Delay structure itself. If the process gets terminated
> while doing this (e.g., adding/removing from SuspendedDelays) the
> whole system is left in an inconsistent state and breaks. http://bugs.squeak.org/view.php?id=6576
> --------
> 0006524: TTFonts can't load unicode character maps
> - http://bugs.squeak.org/view.php?id=6524
> --------
> Font caching
> http://bugs.squeak.org/view.php?id=6089
>
> Something else, that would be good to change is to remove OmniBrowser.
> There are two reasons why I've done this manually for the base image
> of our build process:
> - with the old version of OmniBrowser installed the newer version
> cannot be loaded automatically with Monticello (If I remember
> correctly because there packages have been moved or renamed)
> - for production we need small images (a few MBs per image can make a
> significant difference when running hundreds of images)
>
> Now tell me if some others are important for us.
> I was thinking that Nebraska and Speech could be removed too.
>
> So let me know I will try to do my best to produce 3.9.1

Yes, the pathes to make the latest Yaxo work, see:
See "Yaxo / 3.8.2 / 3.9.1 / 3.10", and "Preliminary new Yaxo version" threads
synch with Mike

from other 3.9.1 threads (GMail rocks):
http://bugs.squeak.org/view.php?id=6768
http://bugs.squeak.org/view.php?id=6512
http://bugs.squeak.org/view.php?id=1602

Also the timeForSpeed and accuratedDateAndTimeNow patches should be
considered IMHO.

Cheers
Philippe

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

keith1y
If you want to use LevelPlayingField as a process to apply and test
these fixes out.

See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.

Then if you produce 3.9 equivalents:

put the bug fixes in http://installer.pbwiki.com/MinorFixes-Squeak3:9
put package upgrades in
http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
put package removals in http://installer.pbwiki.com/Clean-Squeak3:9

Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but with
Installer loaded from squeaksource or
(http://installer.pbwiki.com/f/installer.st ), you can test them all out via

Installer do: 'Latest;Clean'.

or from a command line...

with LPF

#squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer +debug
do="Latest;Clean" SmalltalkImage save="3.9.1"

If you want to see the whole script of what it did...

Installer view: 'Latest'.
Installer view: 'Clean'.

Whether we actually want 3.9.1 to be based upon LPF is worth
considering, since LPF
includes MC1.5, Monticello Configurations, Launcher, and Installer
If we dont then these can be loaded later by LPF for anyone that does
want them. (This is easier than unloading them for people that dont want
them).

To perform this process without LPF, simply load Installer from
squeaksource, perform the Installer do:'Latest;Clean'. and then remove
the class Installer before saving.

Once you have something which works as intended, I myself dont know what
happens next  in terms of update streams and packaging etc.

best regards

Keith

p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
fixes here:
http://squeak310.pbwiki.com/From39To391  Note that the fixes marked as
essential were essential
for the very old LPF to run, as opposed to essential for fixing things.



Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

stephane ducasse
Ok thanks keith I will try to digest what you said.
Could you help me in the process?

Stef

On Feb 1, 2008, at 11:21 PM, Keith Hodges wrote:

> If you want to use LevelPlayingField as a process to apply and test
> these fixes out.
>
> See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
> http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.
>
> Then if you produce 3.9 equivalents:
>
> put the bug fixes in http://installer.pbwiki.com/MinorFixes-Squeak3:9
> put package upgrades in
> http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
> put package removals in http://installer.pbwiki.com/Clean-Squeak3:9
>
> Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but with
> Installer loaded from squeaksource or
> (http://installer.pbwiki.com/f/installer.st ), you can test them all  
> out via
>
> Installer do: 'Latest;Clean'.
>
> or from a command line...
>
> with LPF
>
> #squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer  
> +debug
> do="Latest;Clean" SmalltalkImage save="3.9.1"
>
> If you want to see the whole script of what it did...
>
> Installer view: 'Latest'.
> Installer view: 'Clean'.
>
> Whether we actually want 3.9.1 to be based upon LPF is worth
> considering, since LPF
> includes MC1.5, Monticello Configurations, Launcher, and Installer
> If we dont then these can be loaded later by LPF for anyone that does
> want them. (This is easier than unloading them for people that dont  
> want
> them).
>
> To perform this process without LPF, simply load Installer from
> squeaksource, perform the Installer do:'Latest;Clean'. and then remove
> the class Installer before saving.
>
> Once you have something which works as intended, I myself dont know  
> what
> happens next  in terms of update streams and packaging etc.
>
> best regards
>
> Keith
>
> p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
> fixes here:
> http://squeak310.pbwiki.com/From39To391  Note that the fixes marked as
> essential were essential
> for the very old LPF to run, as opposed to essential for fixing  
> things.
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

stephane ducasse
In reply to this post by keith1y
I like the installer since I'm writing a chapter on it for More Squeak  
by Exmaple but

I'm reading your web pages and I want the fixes to be published on the  
squeakFoundationSqueakSource
as any of the other packages 3.9 published. Then the specification of  
the build should be in the image in
  the scriptloader as any other script. So I do not want to really on  
any different process/tools than for 3.9
for coherence principle. I imagine that you understand why.

Stef



> If you want to use LevelPlayingField as a process to apply and test
> these fixes out.
>
> See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
> http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.
>
> Then if you produce 3.9 equivalents:
>
> put the bug fixes in http://installer.pbwiki.com/MinorFixes-Squeak3:9
> put package upgrades in
> http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
> put package removals in http://installer.pbwiki.com/Clean-Squeak3:9
>
> Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but with
> Installer loaded from squeaksource or
> (http://installer.pbwiki.com/f/installer.st ), you can test them all  
> out via
>
> Installer do: 'Latest;Clean'.
>
> or from a command line...
>
> with LPF
>
> #squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer  
> +debug
> do="Latest;Clean" SmalltalkImage save="3.9.1"
>
> If you want to see the whole script of what it did...
>
> Installer view: 'Latest'.
> Installer view: 'Clean'.
>
> Whether we actually want 3.9.1 to be based upon LPF is worth
> considering, since LPF
> includes MC1.5, Monticello Configurations, Launcher, and Installer
> If we dont then these can be loaded later by LPF for anyone that does
> want them. (This is easier than unloading them for people that dont  
> want
> them).
>
> To perform this process without LPF, simply load Installer from
> squeaksource, perform the Installer do:'Latest;Clean'. and then remove
> the class Installer before saving.
>
> Once you have something which works as intended, I myself dont know  
> what
> happens next  in terms of update streams and packaging etc.
>
> best regards
>
> Keith
>
> p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
> fixes here:
> http://squeak310.pbwiki.com/From39To391  Note that the fixes marked as
> essential were essential
> for the very old LPF to run, as opposed to essential for fixing  
> things.
>
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Philippe Marschall
In reply to this post by stephane ducasse
Personally I would prefer it if 3.9.1 is simply a bug fix release that
builds on tested and tried technology. If LPF makes Stef's job much
easier so be it, but if not then I would prefer it if we could
concentrate on fixes and people who want LPF can load it themselves.

Cheers
Philippe

2008/2/2, stephane ducasse <[hidden email]>:

> Ok thanks keith I will try to digest what you said.
> Could you help me in the process?
>
> Stef
>
> On Feb 1, 2008, at 11:21 PM, Keith Hodges wrote:
>
> > If you want to use LevelPlayingField as a process to apply and test
> > these fixes out.
> >
> > See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
> > http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.
> >
> > Then if you produce 3.9 equivalents:
> >
> > put the bug fixes in http://installer.pbwiki.com/MinorFixes-Squeak3:9
> > put package upgrades in
> > http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
> > put package removals in http://installer.pbwiki.com/Clean-Squeak3:9
> >
> > Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but with
> > Installer loaded from squeaksource or
> > (http://installer.pbwiki.com/f/installer.st ), you can test them all
> > out via
> >
> > Installer do: 'Latest;Clean'.
> >
> > or from a command line...
> >
> > with LPF
> >
> > #squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer
> > +debug
> > do="Latest;Clean" SmalltalkImage save="3.9.1"
> >
> > If you want to see the whole script of what it did...
> >
> > Installer view: 'Latest'.
> > Installer view: 'Clean'.
> >
> > Whether we actually want 3.9.1 to be based upon LPF is worth
> > considering, since LPF
> > includes MC1.5, Monticello Configurations, Launcher, and Installer
> > If we dont then these can be loaded later by LPF for anyone that does
> > want them. (This is easier than unloading them for people that dont
> > want
> > them).
> >
> > To perform this process without LPF, simply load Installer from
> > squeaksource, perform the Installer do:'Latest;Clean'. and then remove
> > the class Installer before saving.
> >
> > Once you have something which works as intended, I myself dont know
> > what
> > happens next  in terms of update streams and packaging etc.
> >
> > best regards
> >
> > Keith
> >
> > p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
> > fixes here:
> > http://squeak310.pbwiki.com/From39To391  Note that the fixes marked as
> > essential were essential
> > for the very old LPF to run, as opposed to essential for fixing
> > things.
> >
> >
> >
> >
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

stephane ducasse
Yes. I do not want to start a new fork (at least not now).
Right now I just want to help people to use 3.9 and include a set of  
crucial fixes
that are needed.

Stef


> Personally I would prefer it if 3.9.1 is simply a bug fix release that
> builds on tested and tried technology. If LPF makes Stef's job much
> easier so be it, but if not then I would prefer it if we could
> concentrate on fixes and people who want LPF can load it themselves.
>
> Cheers
> Philippe
>
> 2008/2/2, stephane ducasse <[hidden email]>:
>> Ok thanks keith I will try to digest what you said.
>> Could you help me in the process?
>>
>> Stef
>>
>> On Feb 1, 2008, at 11:21 PM, Keith Hodges wrote:
>>
>>> If you want to use LevelPlayingField as a process to apply and test
>>> these fixes out.
>>>
>>> See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
>>> http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.
>>>
>>> Then if you produce 3.9 equivalents:
>>>
>>> put the bug fixes in http://installer.pbwiki.com/MinorFixes- 
>>> Squeak3:9
>>> put package upgrades in
>>> http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
>>> put package removals in http://installer.pbwiki.com/Clean-Squeak3:9
>>>
>>> Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but  
>>> with
>>> Installer loaded from squeaksource or
>>> (http://installer.pbwiki.com/f/installer.st ), you can test them all
>>> out via
>>>
>>> Installer do: 'Latest;Clean'.
>>>
>>> or from a command line...
>>>
>>> with LPF
>>>
>>> #squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer
>>> +debug
>>> do="Latest;Clean" SmalltalkImage save="3.9.1"
>>>
>>> If you want to see the whole script of what it did...
>>>
>>> Installer view: 'Latest'.
>>> Installer view: 'Clean'.
>>>
>>> Whether we actually want 3.9.1 to be based upon LPF is worth
>>> considering, since LPF
>>> includes MC1.5, Monticello Configurations, Launcher, and Installer
>>> If we dont then these can be loaded later by LPF for anyone that  
>>> does
>>> want them. (This is easier than unloading them for people that dont
>>> want
>>> them).
>>>
>>> To perform this process without LPF, simply load Installer from
>>> squeaksource, perform the Installer do:'Latest;Clean'. and then  
>>> remove
>>> the class Installer before saving.
>>>
>>> Once you have something which works as intended, I myself dont know
>>> what
>>> happens next  in terms of update streams and packaging etc.
>>>
>>> best regards
>>>
>>> Keith
>>>
>>> p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
>>> fixes here:
>>> http://squeak310.pbwiki.com/From39To391  Note that the fixes  
>>> marked as
>>> essential were essential
>>> for the very old LPF to run, as opposed to essential for fixing
>>> things.
>>>
>>>
>>>
>>>
>>
>>
>>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Janko Mivšek
I also support this quick interim release with most needed patches,
specially those Andreas ones regarding stability of concurrent code.

JAnko

stephane ducasse wrote:

> Yes. I do not want to start a new fork (at least not now).
> Right now I just want to help people to use 3.9 and include a set of
> crucial fixes
> that are needed.
>
> Stef
>
>
>> Personally I would prefer it if 3.9.1 is simply a bug fix release that
>> builds on tested and tried technology. If LPF makes Stef's job much
>> easier so be it, but if not then I would prefer it if we could
>> concentrate on fixes and people who want LPF can load it themselves.
>>
>> Cheers
>> Philippe
>>
>> 2008/2/2, stephane ducasse <[hidden email]>:
>>> Ok thanks keith I will try to digest what you said.
>>> Could you help me in the process?
>>>
>>> Stef
>>>
>>> On Feb 1, 2008, at 11:21 PM, Keith Hodges wrote:
>>>
>>>> If you want to use LevelPlayingField as a process to apply and test
>>>> these fixes out.
>>>>
>>>> See http://installer.pbwiki.com/MinorFixes-Squeak3:10 and
>>>> http://installer.pbwiki.com/MinorFixesUnstable-Squeak3:10.
>>>>
>>>> Then if you produce 3.9 equivalents:
>>>>
>>>> put the bug fixes in http://installer.pbwiki.com/MinorFixes-Squeak3:9
>>>> put package upgrades in
>>>> http://installer.pbwiki.com/PackageUpgrades-Squeak3:9
>>>> put package removals in http://installer.pbwiki.com/Clean-Squeak3:9
>>>>
>>>> Then in a 3.9 image with LPF, or in a 3.9 image without LPF, but with
>>>> Installer loaded from squeaksource or
>>>> (http://installer.pbwiki.com/f/installer.st ), you can test them all
>>>> out via
>>>>
>>>> Installer do: 'Latest;Clean'.
>>>>
>>>> or from a command line...
>>>>
>>>> with LPF
>>>>
>>>> #squeak 3.9.image http://installer.pbwiki.com/f/LPF.st Installer
>>>> +debug
>>>> do="Latest;Clean" SmalltalkImage save="3.9.1"
>>>>
>>>> If you want to see the whole script of what it did...
>>>>
>>>> Installer view: 'Latest'.
>>>> Installer view: 'Clean'.
>>>>
>>>> Whether we actually want 3.9.1 to be based upon LPF is worth
>>>> considering, since LPF
>>>> includes MC1.5, Monticello Configurations, Launcher, and Installer
>>>> If we dont then these can be loaded later by LPF for anyone that does
>>>> want them. (This is easier than unloading them for people that dont
>>>> want
>>>> them).
>>>>
>>>> To perform this process without LPF, simply load Installer from
>>>> squeaksource, perform the Installer do:'Latest;Clean'. and then remove
>>>> the class Installer before saving.
>>>>
>>>> Once you have something which works as intended, I myself dont know
>>>> what
>>>> happens next  in terms of update streams and packaging etc.
>>>>
>>>> best regards
>>>>
>>>> Keith
>>>>
>>>> p.s. when I did my tentative 3.9.1 in Oct 2006, I put a list of bug
>>>> fixes here:
>>>> http://squeak310.pbwiki.com/From39To391  Note that the fixes marked as
>>>> essential were essential
>>>> for the very old LPF to run, as opposed to essential for fixing
>>>> things.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>

--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Philippe Marschall
In reply to this post by stephane ducasse
2008/2/1, stephane ducasse <[hidden email]>:

> Hi all
>
> some people asked if we could produce 3.9.1.
> Here is their list of suggested items:
>
> "We use the following three fixes that are crucial for any server setup:
> 0006581: Image freezes (background processes like Seaside make no
> progress) and Squeak hoggs CPU
> This is the image freezing problem, where connecting with VNC and
> moving the mouse would bring the image alive again. When being stuck,
> Squeak hoggs the CPU, memory consumtion is stable. http://bugs.squeak.org/view.php?id=6581
> Note: fix takes only effect if Preferences enable: #serverMode !
> --------
> 0006588: Broken Semaphore>>critical: leads to frozen processes in Delay
> VNC doesn't respond to UI events, 0% cpu usage, several processes
> frozen in Delay although our Seaside server still responds. http://bugs.squeak.org/view.php?id=6588
> --------
> 0006576: Delay is not thread-safe
> Delay is not thread-safe since currently the calling process updates
> the internal Delay structure itself. If the process gets terminated
> while doing this (e.g., adding/removing from SuspendedDelays) the
> whole system is left in an inconsistent state and breaks. http://bugs.squeak.org/view.php?id=6576
> --------
> 0006524: TTFonts can't load unicode character maps
> - http://bugs.squeak.org/view.php?id=6524
> --------
> Font caching
> http://bugs.squeak.org/view.php?id=6089
>
> Something else, that would be good to change is to remove OmniBrowser.
> There are two reasons why I've done this manually for the base image
> of our build process:
> - with the old version of OmniBrowser installed the newer version
> cannot be loaded automatically with Monticello (If I remember
> correctly because there packages have been moved or renamed)
> - for production we need small images (a few MBs per image can make a
> significant difference when running hundreds of images)
>
> Now tell me if some others are important for us.
> I was thinking that Nebraska and Speech could be removed too.
>
> So let me know I will try to do my best to produce 3.9.1

Fixed Object >> #identityHash
http://bugs.squeak.org/view.php?id=1876

There are at least 3 (!!!) fixes for Interval >> #hash / #equals:
http://bugs.squeak.org/view.php?id=5703
http://bugs.squeak.org/view.php?id=3488
http://bugs.squeak.org/view.php?id=3380

The WeakKeyDictionary might or be interesting or too radical:
http://bugs.squeak.org/view.php?id=6348

Cheers
Philippe

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

stephane ducasse
Philippe it seems to me that these ones may introduce problems. I  
prefer to let that for the next one.\
But thanks for pointing them.

Stef


>> Fixed Object >> #identityHash
> http://bugs.squeak.org/view.php?id=1876
>
> There are at least 3 (!!!) fixes for Interval >> #hash / #equals:
> http://bugs.squeak.org/view.php?id=5703
> http://bugs.squeak.org/view.php?id=3488
> http://bugs.squeak.org/view.php?id=3380
>
> The WeakKeyDictionary might or be interesting or too radical:
> http://bugs.squeak.org/view.php?id=6348
>
> Cheers
> Philippe
>
>


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Philippe Marschall
Sure, that's perfectly understandable.

Philippe

2008/2/2, stephane ducasse <[hidden email]>:

> Philippe it seems to me that these ones may introduce problems. I
> prefer to let that for the next one.\
> But thanks for pointing them.
>
> Stef
>
>
> >> Fixed Object >> #identityHash
> > http://bugs.squeak.org/view.php?id=1876
> >
> > There are at least 3 (!!!) fixes for Interval >> #hash / #equals:
> > http://bugs.squeak.org/view.php?id=5703
> > http://bugs.squeak.org/view.php?id=3488
> > http://bugs.squeak.org/view.php?id=3380
> >
> > The WeakKeyDictionary might or be interesting or too radical:
> > http://bugs.squeak.org/view.php?id=6348
> >
> > Cheers
> > Philippe
> >
> >
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Michael Rueger-4
In reply to this post by Janko Mivšek
Janko Mivšek wrote:
> I also support this quick interim release with most needed patches,
> specially those Andreas ones regarding stability of concurrent code.

A simple way would be to just use the 3.8.x updates modula the ones that
originally came from 3.9.

Michael

Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

stephane ducasse
Thanks mike. (I'm waiting for sophie :))
I'm not sure that I want to put my finger on that but I will check.
I do not what was done in 3.10. and I do not want to give the  
impression I
want to replace what they did. I'm just doing that because of the sema  
fixes and
that people want that in.

Stef

> Janko Mivšek wrote:
>> I also support this quick interim release with most needed patches,  
>> specially those Andreas ones regarding stability of concurrent code.
>
> A simple way would be to just use the 3.8.x updates modula the ones  
> that originally came from 3.9.
>
> Michael
>
>


Reply | Threaded
Open this post in threaded view
|

Re: To prepare 3.9.1

Michael Rueger-4
stephane ducasse wrote:
> Thanks mike. (I'm waiting for sophie :))

Me too ;-)
Slowly getting there...

> I'm not sure that I want to put my finger on that but I will check.
> I do not what was done in 3.10. and I do not want to give the impression I
> want to replace what they did. I'm just doing that because of the sema
> fixes and
> that people want that in.

Same reason why I did 3.8.x.
Maintaining stable versions does not conflict with work on the newer
releases but helps people using Squeak in larger projects a lot.

Michael