You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2010/09/13 12:43:13 UTC
Jackrabbit 2.2.0 release plan
Hi all,
We released Jackrabbit 2.1 in April and there's been a lot of progress
in trunk since then, so I think it's time to start planning for the
2.2 release.
There's a few bigger efforts ongoing in trunk and I'd like to get
things like a Tika 0.8 (hopefully out in October) upgrade included, so
I'd like to initially target November for the release date.
Please use the 2.2.0 label in Jira to tag any issues that you think
are essential for this release. I'll follow up with a more detailed
release plan once we have a better picture of everything we need to do
before the release.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 06/12/10 08:45, Serge Huber wrote:
> Thanks for the graphs. Indeed performance looks a lot better on 2.2
> than 2.1 or 2.0, but in some cases we're still quite slower than
> previous versions. Especially the login/logout test is performing
> poorly, do you have any idea why ?
It's mostly caused by extra setup work used to speed up especially
access control operations later on. See
https://issues.apache.org/jira/browse/JCR-2814 for related work.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Serge Huber <sh...@jahia.com>.
Hello Jukka,
Thanks for the graphs. Indeed performance looks a lot better on 2.2 than 2.1 or 2.0, but in some cases we're still quite slower than previous versions. Especially the login/logout test is performing poorly, do you have any idea why ?
Regards,
Serge Huber.
On 30 nov. 2010, at 10:33, Jukka Zitting wrote:
> Hi,
>
> On 24/11/10 10:49, Jukka Zitting wrote:
>> On 10/11/10 00:13, Jukka Zitting wrote:
>>> After that we'll allow two weeks for testing and fine-tuning in the
>>> branch. Unless any major issues come up, I will then cut the 2.2.0
>>> release candidate on Tuesday, Nov 30th. If all goes well, the release
>>> will be out by the end of that week, at the beginning of December.
>>
>> Let's push that date also ahead, to Tuesday, Dec 7th.
>
> Looks like we're on good track for cutting the release candidate next week, as there's only a bit of tweaking and some minor updates left to be done.
>
> To avoid any unexpected performance regressions, I run the performance test suite last night on the latest 2.2 branch after syncing it with recent changes in trunk. The report looks pretty good, and can be seen at: http://people.apache.org/~jukka/jackrabbit/2.2-20101129/report.html
>
> BR,
>
> Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Serge Huber <sh...@jahia.com>.
Hi Marcel,
I know I could use XPath :) I was just trying to help out on the performance issue :)
From looking at the code, it really looks like there was a lot of effort put into optimizing SQL-1 and XPath, but that we are only at the beginning of the optimizations for SQL-2.
Regards,
Serge Huber.
On 8 déc. 2010, at 09:49, Marcel Reutegger wrote:
> Hi serge,
>
> you could use XPath instead:
>
> root/site//element(*, jnt:news) order by @date descending
>
> regards
> marcel
>
> From: Serge Huber [mailto:shuber2@jahia.com]
> Sent: 08 December 2010 08:51
> To: dev@jackrabbit.apache.org
> Subject: Re: Jackrabbit 2.2.0 release plan
>
>
> Hello Jukka,
>
> I have noticed a performance issue on the ISDESCENDANTNODE constraint which I have reported here : https://issues.apache.org/jira/browse/JCR-2835
>
> I am currently investigating this, but apart from the alternative I proposed in the ticket, I don't see another way of doing this apart from indexing the path at node creation/moving time. Do you have any ideas ?
>
> Best regards,
> Serge Huber.
>
> On 7 déc. 2010, at 13:54, Jukka Zitting wrote:
>
>
> Hi,
>
> On 30/11/10 10:33, Jukka Zitting wrote:
>
> Looks like we're on good track for cutting the release candidate next
> week, as there's only a bit of tweaking and some minor updates left to
> be done.
>
> There are still some clustering tests and other minor things pending, so I'll postpone cutting the release candidate to tomorrow. That'll also give us a chance to do a last performance test run tonight before the release.
>
> BR,
>
> Jukka Zitting
>
RE: Jackrabbit 2.2.0 release plan
Posted by Marcel Reutegger <mr...@adobe.com>.
Hi serge,
you could use XPath instead:
root/site//element(*, jnt:news) order by @date descending
regards
marcel
From: Serge Huber [mailto:shuber2@jahia.com]
Sent: 08 December 2010 08:51
To: dev@jackrabbit.apache.org
Subject: Re: Jackrabbit 2.2.0 release plan
Hello Jukka,
I have noticed a performance issue on the ISDESCENDANTNODE constraint which I have reported here : https://issues.apache.org/jira/browse/JCR-2835
I am currently investigating this, but apart from the alternative I proposed in the ticket, I don't see another way of doing this apart from indexing the path at node creation/moving time. Do you have any ideas ?
Best regards,
Serge Huber.
On 7 déc. 2010, at 13:54, Jukka Zitting wrote:
Hi,
On 30/11/10 10:33, Jukka Zitting wrote:
Looks like we're on good track for cutting the release candidate next
week, as there's only a bit of tweaking and some minor updates left to
be done.
There are still some clustering tests and other minor things pending, so I'll postpone cutting the release candidate to tomorrow. That'll also give us a chance to do a last performance test run tonight before the release.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Serge Huber <sh...@jahia.com>.
Hello Jukka,
I have noticed a performance issue on the ISDESCENDANTNODE constraint which I have reported here : https://issues.apache.org/jira/browse/JCR-2835
I am currently investigating this, but apart from the alternative I proposed in the ticket, I don't see another way of doing this apart from indexing the path at node creation/moving time. Do you have any ideas ?
Best regards,
Serge Huber.
On 7 déc. 2010, at 13:54, Jukka Zitting wrote:
> Hi,
>
> On 30/11/10 10:33, Jukka Zitting wrote:
>> Looks like we're on good track for cutting the release candidate next
>> week, as there's only a bit of tweaking and some minor updates left to
>> be done.
>
> There are still some clustering tests and other minor things pending, so I'll postpone cutting the release candidate to tomorrow. That'll also give us a chance to do a last performance test run tonight before the release.
>
> BR,
>
> Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 30/11/10 10:33, Jukka Zitting wrote:
> Looks like we're on good track for cutting the release candidate next
> week, as there's only a bit of tweaking and some minor updates left to
> be done.
There are still some clustering tests and other minor things pending, so
I'll postpone cutting the release candidate to tomorrow. That'll also
give us a chance to do a last performance test run tonight before the
release.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 24/11/10 10:49, Jukka Zitting wrote:
> On 10/11/10 00:13, Jukka Zitting wrote:
>> After that we'll allow two weeks for testing and fine-tuning in the
>> branch. Unless any major issues come up, I will then cut the 2.2.0
>> release candidate on Tuesday, Nov 30th. If all goes well, the release
>> will be out by the end of that week, at the beginning of December.
>
> Let's push that date also ahead, to Tuesday, Dec 7th.
Looks like we're on good track for cutting the release candidate next
week, as there's only a bit of tweaking and some minor updates left to
be done.
To avoid any unexpected performance regressions, I run the performance
test suite last night on the latest 2.2 branch after syncing it with
recent changes in trunk. The report looks pretty good, and can be seen
at: http://people.apache.org/~jukka/jackrabbit/2.2-20101129/report.html
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 10/11/10 00:13, Jukka Zitting wrote:
> We're getting closer to the release now. I think the big pieces are
> mostly in place already, so I'm planning to create the 2.2 branch next
> Tuesday, one week from now.
After some delays I've now created the 2.2 branch, and Jackrabbit trunk
is now 2.3-SNAPSHOT. I'll review and merge any trunk commits that still
should be included in the upcoming 2.2.0 release.
> After that we'll allow two weeks for testing and fine-tuning in the
> branch. Unless any major issues come up, I will then cut the 2.2.0
> release candidate on Tuesday, Nov 30th. If all goes well, the release
> will be out by the end of that week, at the beginning of December.
Let's push that date also ahead, to Tuesday, Dec 7th.
BR,
Jukka Zitting
RE: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
From: Gadbury [mailto:gadbury@googlemail.com]
> Do you think https://issues.apache.org/jira/browse/JCR-2715 will
> make it in to 2.2.0?
Yes, that's the plan.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Gadbury <ga...@googlemail.com>.
Hi Jukka,
Do you think https://issues.apache.org/jira/browse/JCR-2715 will make it in
to 2.2.0? This is the improvement I am most hoping to make it in :)
Cheers,
James
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Jackrabbit-2-2-0-release-plan-tp2537222p3039982.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Sep 13, 2010 at 1:43 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Please use the 2.2.0 label in Jira to tag any issues that you think
> are essential for this release. I'll follow up with a more detailed
> release plan once we have a better picture of everything we need to do
> before the release.
We're getting closer to the release now. I think the big pieces are
mostly in place already, so I'm planning to create the 2.2 branch next
Tuesday, one week from now.
After that we'll allow two weeks for testing and fine-tuning in the
branch. Unless any major issues come up, I will then cut the 2.2.0
release candidate on Tuesday, Nov 30th. If all goes well, the release
will be out by the end of that week, at the beginning of December.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Sep 13, 2010 at 5:14 PM, Justin Edelson <ju...@gmail.com> wrote:
> Would it be possible to get the patches in JCR-2735, JCR-2737, and
> JCR-2738 applied? These are all trivial patches.
Sure! All patches applied.
BR,
Jukka Zitting
Re: Jackrabbit 2.2.0 release plan
Posted by Justin Edelson <ju...@gmail.com>.
Would it be possible to get the patches in JCR-2735, JCR-2737, and
JCR-2738 applied? These are all trivial patches.
Thanks,
Justin
On 9/13/10 6:43 AM, Jukka Zitting wrote:
> Hi all,
>
> We released Jackrabbit 2.1 in April and there's been a lot of progress
> in trunk since then, so I think it's time to start planning for the
> 2.2 release.
>
> There's a few bigger efforts ongoing in trunk and I'd like to get
> things like a Tika 0.8 (hopefully out in October) upgrade included, so
> I'd like to initially target November for the release date.
>
> Please use the 2.2.0 label in Jira to tag any issues that you think
> are essential for this release. I'll follow up with a more detailed
> release plan once we have a better picture of everything we need to do
> before the release.
>
> BR,
>
> Jukka Zitting