[Q] Is 3.8 really final ?

Lex Spoon lex at cc.gatech.edu
Tue May 17 13:51:21 UTC 2005

"Lic. Edgar J. De Cleene" <edgardec2001 at yahoo.com.ar> wrote:> But
remains problems with SVI what I can't solve.
> >From documentation , could be a Mac specific problem.
> And what about 500 + packages what exist today ?
> All works ?
> I think what all agree what Squeak is a moving target , but I wish move to
> slow speed...

Have you tried, Edgar, to use Services + RB extensions?  If that works,
then RB per se may be come unimportant.

Where should information like this be reported?  I'm sure 3.8's managers
would like to have info on the status of major packages.  Is Mantis the
place?  How about success reports?  Maybe we should do this on the

One thing to keep in mind, is that it may make sense to have a freeze in
order to support external packages catching up.  I've been littered
recently by posts from Debian telling me how to get my packages into the
next release of Debian if they aren't already in.  Irrelevant to me--I
can read the bug tracker and see that my packages are working fine--but
it's useful in general.

I know that at some point we have to draw the line.  IMHO, RB is at
least of borderline importance.  It's a major bragging point of Squeak,
and it's an application that uses text-as-code.  It would be a shame to
ship without one of our best applications, and it would be worrisome
that if RB doesn't work then other applications using text-as-code might
not work either.

But it's a hard decision, and I understand that we can't just sit here
waiting forever.  Some people would rather have 3.8 released even if RB
does not work.  This is something the general community will have to

Finally, I don't buy the "moving target" excuse.  Linux is a moving
target as well, but Debian is very careful with its releases and manages
to ship with thousands of working packages.  New releases tend to be
*more* reliable.  To make this happens requires a basic management
approach -- something that is perhaps unnatural to coders?  What I mean
is, you have to decide wthat you want, measure your progress towards it,
and deal with it whenever your measurements suggest that something is
behind schedule.  The solutions are not generally hard, but you have to
know where you are going and know what your progress is towards it.


More information about the Squeak-dev mailing list