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

Avi Bryant avi at dabbledb.com
Mon Feb 26 21:53:48 UTC 2007

On 2/26/07, Philippe Marschall <philippe.marschall at gmail.com> wrote:

> It's just that Monticello doesn't support this. The Monticello
> filename hacks have to stop.  For example the filename hacks of
> Chronos wreck havoc on the Monticello Browser. An other example my
> Monticello marks Seaside2.8a1 as if there was a new version that I
> haven't loaded which isn't the case. Additionally they make the
> Seaside repository even more crowded.

So I agree with you that the filename hacks are silly.  That said,
Package.branch-author.99 works pretty well as a format.  For somewhat
annoying historical reasons, "Seaside2" is our package name.  Why
don't we acknowledge that we don't really "do" releases, and just have
a Seaside2.stable branch, and then various meaningfully named
Seaside2.foo branches.  For example, a lot of the 2.7 work could have
been classified as Seaside2.canvas-only or some such.  That's what we
do for Dabble, and it's worked well (we're probably past 10k commits
at this point).  The MC browser splits the repository up on branch
name (it considers them all separate packages), which keeps clutter
under control.

Either that, or have a separate "stable" repository and copy stuff
into that when it's ready, but that seems like more work to me.


More information about the Seaside mailing list