From: "Andreas Hartmann" <[EMAIL PROTECTED]>
Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
I think it will add to stability, because having JCR integrated is a
major
feature and an incentive for people to use Lenya and therefore leading
to
maturity.
?
just ask yourself why should anyone use 1.4 ...
- publication templating
- usecase framework
- transactions
Dear Developers
I could imagine that we're upgrading to Lenya 1.4 at the beginning of the
next year. (We first need to finish another project.) The reasons for this
are the ones that Andreas mentioned. I also expect Lenya 1.4 to be (in the
end) more stable because of it's more general architecture.
Since we're running the websites of about 50 units at our University, Lenya
1.4 really needs to be stable for that we can upgrade. Having Lenya 1.4
already in September gives us time to test it, and to adjust our publication
type to it.
I prefer stability to JCR integration. And if the upgrade to 1.4 without JCR
integration becomes easier - the better!
+1 to Andreas proposal how to proceed
-michael
and do people want again
having to migrate their data and functionality to another content API for
a
future version (e.g. 1.6).
That's an interesting issue. 1.4 is scheduled for September 2005.
Actually I doubt that we can get the JCR integration to a state
which is so stable that we can keep it in 1.6 without breaking
backwards compatibility. Even if we can hide it behind a Lenya
specific repo API, we probably have to do some modifications to
that one.
I'd suggest that we fix the remaining bugs in 1.4 (which is quite a
lot to do), get it out as soon as possible, close 1.2 and start a
1.6 branch with JCR integration. If people don't consider it worth
upgrading to 1.4, they can wait for 1.6.
But, well, maybe I change my mind when I actually work with JCR
and see if it's really that easy to integrate.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
