On Tue, Feb 17, 2009 at 6:30 AM, Jukka Zitting wrote:
>
> Dan, I hope you'll be OK with a custom build for now until Jackrabbit
> 1.6 is out?
>
That is fine.
I know I need to clean up the patch yet and get it back, but I've been busy
fighting fires this week. Expect something in the next couple d
Hi,
On Tue, Feb 10, 2009 at 5:00 PM, Jukka Zitting 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
Hi,
On Mon, Feb 16, 2009 at 11:54 AM, Marcel Reutegger
wrote:
> On Mon, Feb 16, 2009 at 09:14, Marcel Reutegger
> wrote:
>> I'll have a look at the patch today and provide feedback.
>
> this feature also requires changes to jackrabbit-spi-commons. that's
> where the query parsers are located. II
On Mon, Feb 16, 2009 at 09:14, Marcel Reutegger
wrote:
> I'll have a look at the patch today and provide feedback.
this feature also requires changes to jackrabbit-spi-commons. that's
where the query parsers are located. IIUC, the plan is to just release
a jackrabbit-core 1.5.3, right?
I think w
On Sat, Feb 14, 2009 at 9:30 PM, Jukka Zitting wrote:
> I'd like to hear especially from Marcel, who knows the query system
> best.
I'll have a look at the patch today and provide feedback.
regards
marcel
Hi,
On Sat, Feb 14, 2009 at 7:55 PM, Dan Diephouse
wrote:
> Do I have a choice? :-)
In fact you do. On a few occasions we have bended the release policies
a bit in cases like yours where an external product release depends on
some specific feature in Jackrabbit.
So we could consider doing somet
Do I have a choice? :-) Ideally we could get it in 1.5.3 soon and depend on
it so we can use it in the next update of our product which is coming out
soon. (within a month) However, I understand the realities of the release
process as well. So if it doesn't make it in 1.5.3, we'll use our own pat
Hi,
On Sat, Feb 14, 2009 at 1:32 AM, Dan Diephouse
wrote:
> I've attached a patch for https://issues.apache.org/jira/browse/JCR-1659
Nice! This feature is something I think many people have been missing at times.
> it would be awesome if we could get that in the 1.5.3 release.
We generally avo
Hi Jukka,
I've attached a patch for https://issues.apache.org/jira/browse/JCR-1659 and
it would be awesome if we could get that in the 1.5.3 release.
Cheers,
Dan
On Tue, Feb 10, 2009 at 8:00 AM, Jukka Zitting wrote:
> Hi,
>
> Fixes are again accumulating in the trunk and there seems to be some
>
Hi,
On Thu, Feb 12, 2009 at 8:04 PM, Grégory Joseph
wrote:
> I'm trying to figure out what causes JCR-1952 - unless it's something stupid
> on my part, it seems pretty much like a blocker bug, even though it doesn't
> happen on all platforms.
Agreed, that's a pretty serious issue, though it only
Hi,
On Thu, Feb 12, 2009 at 7:57 PM, Sandro Boehme wrote:
> if that https://issues.apache.org/jira/browse/JCR-1959 would be easy to
> solve it would be nice if it would be part of the 1.5.3 realease.
Looks like this could be a classpath issue. See my comment on the issue.
BR,
Jukka Zitting
Hi,
On Thu, Feb 12, 2009 at 11:18 AM, philipp_s wrote:
> http://issues.apache.org/jira/browse/JCR-1554 but I think this already in...
Yes. Here's the list of fixes I've already merged to 1.5.3.
[JCR-1334] Deadlock due different Thread access while prepare and commit ...
[JCR-1554] StaleItem
I'm trying to figure out what causes JCR-1952 - unless it's something
stupid on my part, it seems pretty much like a blocker bug, even
though it doesn't happen on all platforms.
Cheers,
-g
https://issues.apache.org/jira/browse/JCR-1952
On Feb 10, 2009, at 5:00 PM, Jukka Zitting wrote:
Hi
Hi Jukka,
if that https://issues.apache.org/jira/browse/JCR-1959 would be easy to
solve it would be nice if it would be part of the 1.5.3 realease.
Bye,
Sandro
Jukka Zitting schrieb:
Hi,
Fixes are again accumulating in the trunk and there seems to be some
demand for a new patch release. So
http://issues.apache.org/jira/browse/JCR-1554 but I think this already in...
thx!
Philipp
--
View this message in context:
http://www.nabble.com/Jackrabbit-1.5.3-release-plan-tp21936668p21973262.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Hi,
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.
I'll be going through the issue tracker for candidate fixes to be
included in the 1.5 branch, but any input on what fixes you'd like to
see in
16 matches
Mail list logo
