[squeak-dev] Pending 4.1 Mantis Bugs

Alexander Lazarević laza at blobworks.com
Thu Apr 8 15:49:37 UTC 2010

I just went through some issues on mantis (boy there is stuff in there
and it certainly sends you on a roller coaster tour visiting places in
Squeak I never ever have touched).

I added 7453, 7157 just in case, but maybe this is already covered by
the new VMs. Feel free to remove them again from the list.


2010/4/8 Andreas Raab <andreas.raab at gmx.de>
> Folks -
> Even though we were late with getting our tests green, the Mantis status for the 4.1 bug list looks pretty promising (http://bugs.squeak.org/view.php?id=7480). I just did a pass to resolve the issues that could be reasonably resolved and it basically leaves us with three remaining issues:
> [7472] In sq 9563 copying workspace text across images loses line endings
> http://bugs.squeak.org/view.php?id=7472
> This looks like a Linux / Unix bug. I have absolutely no idea what (if anything) to do here. Someone please advise.
> [7424] the ProportionalSplitterMorph in ArchiveViewer is out of service
> http://bugs.squeak.org/view.php?id=7424
> This is an interesting bug. Morph>>containingWindow, the root of the problem used to be a very simply method but got replaced with something significantly more complex. Does anyone recall what the reason for that replacement was? It appears to me that replacing all the logic with a simple "self findOwnerSuchThat:[:m| m isSystemWindow]" ought to be correct but I'm virtually certain that there must be some reason for the logic in there and I don't feel very good about replacing some complex logic like that so shortly before the release. Any insights are welcome.
> [7463] In sq 8955 ChangeSorter has a multiple number of ailments
> [7342] Change Sorters in 3.10.2 no longer report about class definitions or class comments.
> [7443] In sq 8864 Changesorter shows changeset name twice after loaded from project.
> http://bugs.squeak.org/view.php?id=7463
> There is whole bunch of ChangeSorter issues that I am uncertain about. Some of the comments indicate that portions may have been fixed or should have been fixed, but I am uncertain what, if any, action to take.
> The key question to me here is: Which one of these are show-stoppers? Which one of these stop you from getting work done, make work results inaccessible or similar?
> In any case, it's nice to see that we're down to five issues to resolve for 4.1. Thanks everyone for your help!
> Cheers,
>  - Andreas

More information about the Squeak-dev mailing list