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

Boris Popov boris at deepcovelabs.com
Mon Feb 26 21:18:26 UTC 2007

Ditto; as an outside developer it's important for me to be able to tell
which versions are considered stable and which versions are in flux
while major refactoring is underway and there isn't a way to tell that
at the moment, is there? There's nothing wrong with the process that you
have, it's just that we'd like to know a little more about where things
are at any given time and I thought including that bit of extra context
in the version number may be the least impact solution for everyone, but
ultimately it's up to you anyhow.


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Avi Bryant
> Sent: Monday, February 26, 2007 1:09 PM
> To: The Squeak Enterprise Aubergines Server - general discussion.
> Subject: Re: [Seaside] So where is the "release" version of 3.7?
> On 2/26/07, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> > That's not how Seaside is developed. We don't have such cycles. As
> > Lukas said, in general we use the latest Seaside version for
> > production applications and we certainly develop Pier and Magritte
> > against the latest version. You can't do that if you have open bugs
> > that you know about. Sure there are instable phases when a lot of
> > refactoring is going on (like start of 2.7 or lr.171+) but that's in
> > general only maybe 4 versions. If we know about a bug, we fix it, if
> > we want a feature, we implement it. This is how Seaside is
> > This is why it is pointless to attach a label to a Seaside version.
> Ok, but there are processes that work for that too.  Have a branch
> that is 2.7-stable, and generally commit to that.  If you're doing a
> refactoring or feature you're not sure about, do it on
> 2.7-somerefactoring, then merge in when you're confident of it.  The
> important thing is just that everyone know what the system is.
> Avi
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list