We should only use externals to projects with own release cycles. The
idea of breaking out the blocks from trunk was to start considering them
as separate projects with separate release cycles.
The when we do a "compound" release of Cocoon core together with all
blocks, all the externals in the taged compound release should point to
tagged releases of the blocks.
This certainly isn't our current practice. But I think we need to start
considering the blocks like separate projects sooner rather than later.
Its time that we stop thinking about Cocoon as one huge beast where
everything is connected to everything else. First it isn't, and second
it doesn't scale at all.
Thinking more about it: with the wild card includes for configurations
and sitemaps, is there still anything that prevent us from having binary
releases?
/Daniel
Bart Molenkamp wrote:
Sorry, hit the send button too early...
You can specify a revision within the svn:external property. Something
like (got this sample from the svn book):
third-party/skins/toolkit -r21 http://svn.red-bean.com/repos/skin-maker
So I think, when you've labelled cocoon 2.1.8, you should change the
svn:externals property in that tag one more time an let it point to the
CForms block with the same revision number as the revision that
committed the tagging of version 2.1.8, right?
Bart.
-----Oorspronkelijk bericht-----
Van: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
Verzonden: vrijdag 23 september 2005 11:49
Aan: Cocoon-Dev
Onderwerp: [RT] Are svn externals a good idea?
I'm just wondering if svn externals are a good idea wrt to
versioning.
I just had to checkout an older version of 2.1.8-dev and checked out
that particular revision. Now unfortunately, the jcr block (and now
the
forms block) is linked into the tree using a svn external. And
although
I checked out an old version of the cocoon tree, I get the latest
version from the jcr block. So it's not that easy to get the exact
version of the whole tree. Or is there an easy way?
And what does this mean wrt to tagging a release (which is a copy of
the
source tree)?
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
