[Seaside] Seaside 2.7a1 versions 169

Jason Johnson jbjohns at libsource.com
Wed Feb 28 17:38:25 UTC 2007

I haven't been able to follow this thread very well because of my
mailer, but my take on this is:  MC is a repository like CVS, darcs or
something.  If you are looking for a "head" version, then it sounds to
me like you are looking for a package manager.  I don't think MC does
this, and I don't know if it should.  But there are tools that do.  What
Seaside needs is to have a "universe" made for it, and when a new stable
version is checked in and "blessed" then the version gets updated in the

Even if everyone was strict with the branching in MC to have a dev
branch and stable branch that still doesn't help you at all (well, I
don't know if MC can, but CVS, et al can't) with dependencies the way
universes or something similar can.

Lukas Renggli wrote:
>> path.  This is to make it easy for the maintainers (anyone who merges
>> regularly in the repository) to consider code.  I am free to post
>> something bogus to the repository and for it to ultimately cause a
>> discussion but no merge.  So I would agree with Philippe that the top
>> number has no semantics.  You might have been very fortunate in the
>> past the the 'head' revision has always been merged by lukas/philippe/
>> michel/avi/whoever and therefore you can trust it because you trust
>> these people.  I have had a head revision in the past but I wouldn't
>> trust it; it's just a side effect of the upload before a maintainer
>> merges it.  Lukas/Philippe do you see it this way?
> Yep, exactly. Nice write-up.
> And in case of doubts or problems there is always the mailing-list
> where we can discuss about the changes.
> Cheers,
> Lukas

More information about the Seaside mailing list