Bob Harner wrote:
Okay, but for my own education can anyone explain why this is the
preferred approach? Doesn't it mean that everytime you want to do a
release you have to first either 1) wait for the next release of
Cocoon, or 2) fall back to the most recent Cocoon release and then do
a great deal of testing on a previously unsuppoprted combination of
Lenya/Cocoon and fix/remove anything that depends on the unreleased
Cocoon code? That makes releases harder (and less frequent?). Also,
developers are then subjected to unexpected bugs introduced by new
Cocoon code. Finally, it means that every Lenya developer is working
from a (slightly) different version of the Cocoon trunk, so a Lenya
svn update can cause breakage too.
very much agreed. but IIRC we agreed on the following:
Lenya 1.4-dev is based on Cocoon-2.1.9-dev resp. BRANCH_2_1_X
Lenya.1.2.5-dev is based on Cocoon 2.1.8
which means for the stable Lenya branch (1.2.x) we do rely on a stable
Cocoon version,
whereas for the unstable Lenya branch (1.4.x) we do rely on the unstable
Cocoon version.
As soon as Lenya 1.4.x stabilizes we should switch to stable Cocoon
versions.
It seems to me the only benefit to developing with the Cocoon trunk is
so that the developers can "work ahead" to make Lenya work with
upcoming Cocoon changes.
I understand that the Lenya PMC may decide that a particular key
feature of a not-yet-released version of Cocoon is critical to the
next release of Lenya. That makes sense, and it's what seems to have
happened recently with the new JCR functionality which will be in
Cocoon 2.1.9. But once 2.1.9 is out...
well, we had a lot of discussions and I personally would favor relying on
stable Cocoon versions, but the community agreed otherwise (at least if
I didn't
misunderstand something completely).
But as Andreas was pointing out we can always release on a particular
Cocoon revision
and make this available through the Lenya website. For instance we as
company
are using the methodology of so-called vendor branches to guarantee that
we don't
have a problem if something might be broken within Cocoon or Lenya.
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
