[Seaside] Seaside 2.7a1 versions 169
Michael Roberts
mike at mjr104.co.uk
Mon Feb 12 20:46:44 UTC 2007
I agree with the general sentiments on both sides of the thread, but
I am not sure I find this correct:
> I only suggest that since
> posting to the main path is intentional it should be respected and
> that not
> bothering to include someone else's changes is bad form.
My understanding from talking to Lukas and Philippe is that anyone
can post to SqueakSource/Seaside if that is what you mean by the main
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?
What I assume Philippe is saying is that we need some meta
information in monticello to say 'this' version is the official one.
I don't know if MCC does this or not. In the past this has been done
either via SM releases or more currently via Lukas' installer. I am
not sure there is any point to marking individual versions of
monticello projects official or not. Increasingly, projects are
dependent on other projects and therefore they need to be grouped to
have useful meaning. Is that MCC or does MCC do something else, or a
subset?
Cheers,
Mike
More information about the Seaside
mailing list