[Seaside] So where is the "release" version of 3.7?

[Jason Johnson]

No.  It's not.  SqueakMap is basically a repository for every package 
ever.  Afaik, it maybe be able to get the latest version but it can't 
determine dependencies, which leaves you to create your SM package plus 
another that can download it.  I mean, I appreciate the work Lukas has 
done and at the moment that is what I always use to bootstrap a new 
system with Seaside/Pier/Magritte.  But thinking long term, is a special 
squeak map script scalable?  Is it composable with other such scripts?  
I think a separate system designed for pure package management would be 
the best.

I think this issue is coming up a lot for several different packages.  
Enough to show that the current solutions are not working.  And I am not 
saying anything against Lukas or Philip.  We just need to get a system 
that can stay out of their way and let them do what they do. :)

Damien Cassou wrote:
> 2007/2/28, Jason Johnson <jbjohns at libsource.com>:
>> I think the ad-hoc release culture that seaside currently has is a huge
>> benefit and advantage.  Lukas usually has what ever bug I find fixed
>> before I get the email update.  What needs to stop is the need of
>> updating from Monticello.  Other open source projects use CVS or
>> Subversion, but when you go to their site how many recommend you
>> download from the repository?  Most give it as an option, but nearly all
>> have a separate place for getting the latest
>> stable/unstable/foo-only/etc.  This what needs to get adopted and this
>> would allow folks that are in a position to know to update the package,
>> so that people who can't keep up with it don't have to.
>
> This is what SqueakMap is for.
>