jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister" <dominique.pfis...@day.com>
Subject Re: Jackrabbit 1.5 release plan
Date Fri, 18 Apr 2008 09:59:04 GMT

Speaking of major changes with respect to JCR 2.0 and whether
introducing them into JR 1.5 makes sense, I'm in favor of introducing
new features that do not affect existing code (let alone break the
build) and that are backed by some basic tests (that will of course
not cover every conceivable scenario). When users are going to use
these features to some extent, they will probably stumble across some
bugs, but that way they are discovered much quicker.


On 18/04/2008, Felix Meschberger <fmeschbe@gmail.com> wrote:
> I honestly don't know and if the changes are really not build-breaking,
>  the better.
>  But the wording "... these new features only need to stable enough that
>  they don't break things if people are *not* using them..." kind of
>  worried me and caused my branch discussion. Because if something is in
>  there, chances are that people are going to use it. And telling them in
>  bugs, that they should not use it yet because it is unfinished work kind
>  of sounds not good.
>  Regards
> Felix

View raw message