Michael Wechner wrote:
[...]
- publication templating
- usecase framework
- transactions
you mean transactions for usecases?
These features are great, but how does the "user" see the actual
incentive ...?
No, the intention is that she doesn't see anything :)
But she will see that transactions are missing in 1.2 when
corrupt content occurs (just imagine someone changing a file
during the link rewriting task ...)
Are these features thouroughly tested within production?
No.
is September really realistic?
IMO yes.
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.
why? JSR-170 is final! It's just implementing the API
I didn't mean the JCR API but the Lenya repository API.
We learn from mistakes, requirements will change ... it's hard to keep
an API stable under these circumstances.
Even if we can hide it behind a Lenya
specific repo API, we probably have to do some modifications to
that one.
why?
See above. I hope that I will be proved wrong :)
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.
we cannot close 1.2 until 1.4 is mature and running in production for
various publications. When will be that the case? In a year? In two years?
Yes, good point ...
But if we don't stop adding features to 1.4, when will we get
out a next release at all?
But, well, maybe I change my mind when I actually work with JCR
and see if it's really that easy to integrate.
Please don't get me wrong, but to be honest I think most people here have
never really done anything with JCR, so how can one judge?
Lurking on the jackrabbit list suggests it's rather not a piece of cake ...
But again, I hope I'm wrong :)
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
