Hi, On Tue, Feb 10, 2009 at 5:00 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Fixes are again accumulating in the trunk and there seems to be some > demand for a new patch release. So I'm planning to do a 1.5.3 release > next week.
See below for the list of fixes currently going to the 1.5.3 release. [JCR-1334] Deadlock due different Thread access while prepare and ... [JCR-1554] StaleItemStateException with distributed transactions [JCR-1889] Incorrect support for java interfaces in typed collection fields [JCR-1923] Startup fails if clustered jackrabbit is upgrade from 1.4.4 to 1.5 [JCR-1941] AccessManager asks for property (jcr:created) permissions ... [JCR-1956] Database Data Store: close result sets [JCR-1970] populate.jsp uses Java 1.5 method [JCR-1979] Deadlock on concurrent read & transactional write operations There's still some testing of JCR-1979 going on that's keeping me from cutting the release. I unfortunately haven't had time to look deeper at JCR-1959, so that issue will most likely not be fixed in the release. Also, as discussed, the JCR-1659 feature will not be included. The XML serialization issue JCR-1952 is a borderline case. We have two reasonable options on how to fix that, but I'm afraid that both carry a notable risk of introducing other regressions. Would people be fine if we postponed the fix to 1.5.4 in March? This way we'd have more time to consider the alternatives. Meanwhile there's the not-so-nice-but-working workaround noted in the issue. Putting all this together, we won't have the release out this week. My current plan is to cut the release over the weekend, which should make the release officially available later next week. BR, Jukka Zitting
