Yeah - it's a fair point. The problem with the deadlock-related stuff
is that it's not such an easy job to contribute in this area. The
locking code is distributed widely throughout the core, and ideally
what's required is a design rethink for the versioning functionality
in jackrabbit. While other bug-fixes are quite reasonable to expect
contributions for, deadlock is almost inevitably going to need to be
sorted out by the longer-standing developers I think.

I'm persuaded re: releasing 1.1, though, I'm just concerned that this
issue is dragging along and I can't see an easy way to get it fixed.
In our case the only workaround has been to single-thread the entire
application and put up with total user lockout during long-running
transactions.

br,

miro

On 10/6/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,

On 10/6/06, Miro Walker <[EMAIL PROTECTED]> wrote:
> [x] -1 Don't release until deadlock-related issues are fixed (e.g.
> JCR-546). It just strikes me that major stability issues such as these
> in the core of Jackrabbit should be dealt with as a priority before
> further releases. Of course if the fix time is too long, then perhaps
> that's not possible...?

I'd downgrade JCR-546 from Critical to Major, since the issue only
affects use cases with concurrent versioning operations. It's also
been open since August, and I don't see any immediate action being
taken on it (contributions are welcome :-).

Apart from that, there are always going to be open issues in an
actively developed software product. The 1.1 release contains a large
number of fixes and features that are very useful for a large
audience, and I see no reason why we should delay getting those out
just because of some open issues. It's not like 1.1 will be the last
Jackrabbit release, I'll probably do a 1.1.1 later on and would like
to have 1.2 out at the end of the year.

The only issues I'd consider as real blockers are legal issues like
JCR-573 and technical issues that cause Jackrabbit to fail the JSR 170
TCK.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development

Reply via email to