CALL FOR 3.9 Final changes

Hi all

next week we will gather at my place and work on 3.9 final.
We would ****really**** appreciate that the other package maintainers
mention the new versions of packages for 3.9.

This is the third time I asked and so far I got nearly no feedback  
except
from the network and morphic packages maintainer. May be we should  
fork for the other packages.

If you have important bugs fixes that you want to see harvested  
please reply to this email
and put link to the mantis entry.

Stef

2006/7/6, stéphane ducasse <[hidden email]>:
Fix extremely slow (O(N)) Dictinaries and Sets

http://bugs.impara.de/view.php?id=1876

Philippe

On Thu, 06 Jul 2006 10:23:45 +0200, Philippe Marschall  
<[hidden email]> wrote:


Add new callback features by Andreas.

--
www.lethalman.net - Thoughts about internet technologies

Number parser http://bugs.impara.de/view.php?id=3512
And all the little no important bugs I've submitted

Hi Stef -

I'll need the weekend to do some finishing touches (there are some open
bugs that I want to have a final look at to decide whether it's worth
fixing them for 3.9 or to postpone them). I'll send a note as soon as
I'm done with it.

Cheers,
   - Andreas

stéphane ducasse wrote:

  http://bugs.impara.de/view.php?id=4078

--Tom Phoenix

A general note:
I don't know if this only me, but the __MACOSX folders in the zip are
__really annoying if you're not on a Mac. I'd appreciate it, if we
could get rid of them in the final release.

Philippe

2006/7/6, stéphane ducasse <[hidden email]>:

On 7/6/06, Philippe Marschall <[hidden email]> wrote:
> I don't know if this only me, but the __MACOSX folders in the zip are
> __really annoying if you're not on a Mac. I'd appreciate it, if we
> could get rid of them in the final release.

I'ts not only you. This is MasOS's way to encapsulate his resource
forks so that it's not lost on other OSs.

zip (command-line) has an option -df to only include the data forks in
the archive.
Else the folders can be removed afterwards with something like zip -d
foo.zip __MACOSX\*

--
 Damien Pollet
 type less, do more

Excellent!!!!!
I'm currently going over the bugs I'm aware off (but I was away a week).
I will make a to do list and with marcus and diego we will try to  
work like mad next week :)
Just let us know.
Stef

On 6 juil. 06, at 18:48, Andreas Raab wrote:

Ok I will try.

Stef

On 6 juil. 06, at 20:34, Philippe Marschall wrote:

Minor fixes but usefull, tested and ready to use:

http://bugs.impara.de/view.php?id=3564
http://bugs.impara.de/view.php?id=3568

Please...

Nicolas

Hi tom

do you have a list of tests that you fixed and that I could harvest?
Because if I remember you were fixing some of them.

Stef

On 6 juil. 06, at 20:25, Tom Phoenix wrote:

>  http://bugs.impara.de/view.php?id=4078
>
> --Tom Phoenix
>

Philippe

which cs exactly should I load?

Stef

On 6 juil. 06, at 10:23, Philippe Marschall wrote:

Hi Stef -

I spent today going over all of the various fixes and changes and
produced what (hopefully) is a consistent set of changes. I say
"hopefully" because in the process of working on the various parts I
found that the in-image changes at times conflicted with other changes,
and that some of these changes were not appropriate (please, if we talk
about communication, how about the release makers telling the package
maintainers that they've changed a package?). As a result of this
process, I've decided that from now on I have will have a very clear
policy about including fixes, namely:

With the exception of critical fixes (that is fixes without which the
system would severely break) I will no longer accept changes that do not
  go through the approved process, e.g., via Mantis. That is both, for
my own sanity as a gesture of fairness towards the people who spend time
and effort reporting the bugs on Mantis. I find it deeply unfair if some
people have to go through a vetting process (in which I regularly reject
changes) and others just get a ride for free on the back of some changes
that just "somehow" end up in the image.

The latest version of the packages are here:
   http://source.squeakfoundation.org/Balloon/Ballon-ar.13.mcz
   http://source.squeakfoundation.org/Balloon/Flash-ar.5.mcz
   http://source.squeakfoundation.org/Balloon/TrueType-ar.4.mcz
   http://source.squeakfoundation.org/Compression/Compression-ar.8.mcz
   http://source.squeakfoundation.org/FFI/FFI-ar.11.mcz
   http://source.squeakfoundation.org/Graphics/Graphics-ar.38.mcz
   http://source.squeakfoundation.org/Graphics/GraphicsTest-ar.9.mcz
They mostly include the various bug fixes and merges of changes that
were already in the image (if SqF would have the log-button I'd include
the change logs... ;-)

For this round of changes there is an odd inconsistency here which I
realize but it was only in the process of looking at proposed changes
that I came to realize that in an "orderly" process I would have
rejected some of those changes outright. So, in this round there are
still various changes included that went outside the regular processes,
in the future I will not longer accept those. I have started to reject
some changes though (those that triggered the whole process, like the
one making Color depend on NaturalLanguageTranslator), so you will want
to make sure that the following bugs are properly dealt with:

        http://bugs.impara.de/view.php?id=4166
        http://bugs.impara.de/view.php?id=4168
        http://bugs.impara.de/view.php?id=4169
        http://bugs.impara.de/view.php?id=4170

With these four bugs fixed the packages should be nicely in sync.

Cheers,
   - Andreas

Hi andreas

I will update and release a new version this morning then.
Do you really think that the 600k changes of diego could go via mantis?
We were more than happy to see Smallland fork merged back in Squeak.
And I know what is to work with conflicts and changes that are not  
yours. I deal with that all the times.

Stef

What is a log-button?
You mean what bert introduced in SqueakSource?

> For this round of changes there is an odd inconsistency here which  
> I realize but it was only in the process of looking at proposed  
> changes that I came to realize that in an "orderly" process I would  
> have rejected some of those changes outright. So, in this round  
> there are still various changes included that went outside the  
> regular processes, in the future I will not longer accept those. I  
> have started to reject some changes though (those that triggered  
> the whole process, like the one making Color depend on  
> NaturalLanguageTranslator),

Berk! Who did that?

> so you will want to make sure that the following bugs are properly  
> dealt with:
>
> http://bugs.impara.de/view.php?id=4166
> http://bugs.impara.de/view.php?id=4168
> http://bugs.impara.de/view.php?id=4169
> http://bugs.impara.de/view.php?id=4170
>
> With these four bugs fixed the packages should be nicely in sync.

I'm confused. Should I harvest them. I guess yes.

Stef

Hi Stef -

> I will update and release a new version this morning then.
> Do you really think that the 600k changes of diego could go via mantis?

Perhaps not. But a useful way of dealing with these changes would have
been to file a bugreport that says "okay, we got all these changes that
nobody really looked at, could you go over the changes in the graphics
package and deal with them appropriately".

Yes. It's really useful.

>> I have
>> started to reject some changes though (those that triggered the whole
>> process, like the one making Color depend on NaturalLanguageTranslator),
>
> Berk! Who did that?

It is actually not that suprising (and I've seen much worse code). It
comes from Color>>colorPaletteOfDepth: which uses
NaturalLanguageTranslator for some form substitution. But you can
probably see why I'm starting to reject such changes - these
dependencies shouldn't be in the graphics package, in particular
considering that all users of it are in Morphic (which is why I moved
this to ColorPickerMorph).

>>     http://bugs.impara.de/view.php?id=4166
>>     http://bugs.impara.de/view.php?id=4168
>>     http://bugs.impara.de/view.php?id=4169
>>     http://bugs.impara.de/view.php?id=4170
>>
>> With these four bugs fixed the packages should be nicely in sync.
>
> I'm confused. Should I harvest them. I guess yes.

Or leave them to the appropriate package maintainers to deal with, just
keep an eye on those changes. Without them fixed you got some series
issues with 3.9.

Cheers,
   - Andreas

>> I will update and release a new version this morning then.
>> Do you really think that the 600k changes of diego could go via  
>> mantis?
>
> Perhaps not. But a useful way of dealing with these changes would  
> have been to file a bugreport that says "okay, we got all these  
> changes that nobody really looked at, could you go over the changes  
> in the graphics package and deal with them appropriately".

Ok I will take note of that for the future.
Ok I will ask the squeaksource guy if they can update it.

Ok good.
I was thinking that it would be good to have a way to understand  
dependencies. We will start to work on it for a research
topics and I hope to fold the results into a kind of tool for squeak.

I would like to have 3.9 final (or nearly there) by the end of next  
week.

Stef

On 9-Jul-06, at 2:51 AM, stéphane ducasse wrote:


>
> I would like to have 3.9 final (or nearly there) by the end of next  
> week.

I think what you're putting together here is 3.9 gamma, not final.  
Once you're done it really needs a least a few weeks when people can  
test it before any crucial repairs are installed if they are needed.  
If everyone is reasonably happy without any changes being made then  
we can rename -gamma to -final with a clear conscience.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- Monorail doesn't go all the way to Tomorrowland.

Sure! (I never dreamed about that but this was a secret).
But this way we get some more pressure :)

Hi andreas

I prepared all the scripts for the integration and when I run it (you  
can do an update from the latest image)
MC does not find Balloon-bf.3.mcz (an ancestor of Balloon-ar.11).  
Could you have a look?
May be I could load without merging (but I do not know the complete  
implication).

Stef