Hi,
Here's hoping we'd finally be ready for the release... We've resolved
both JCR-422 and JCR-1972 and all the other issues people have been
asking for the 1.6 release.
I've just created the 1.6 branch and started preparing the release
notes. Unless anything major comes up, I'm planning to cut
On Wed, Jul 8, 2009 at 11:37, Jukka Zittingjukka.zitt...@gmail.com wrote:
Let me know if there's anything missing from the 1.x branch that you'd
like included in the 1.6.0 release.
FYI, I've merged the changes for JCR- into the 1.x branch.
regards
marcel
Hi,
On Mon, Jun 29, 2009 at 12:36 PM, Martijn Hendriksmarti...@gx.nl wrote:
Is it possible to include JCR-2129, JCR-2138 and JCR-2168 in jackrabbit 1.6.0?
Yes, I merged them all to the 1.x branch yesterday.
I'm now planning to move forward with the 1.6.0 release, even if the
backup/migration
Great, thanks!
Martijn
Van: Jukka Zitting [jukka.zitt...@gmail.com]
On Mon, Jun 29, 2009 at 12:36 PM, Martijn Hendriksmarti...@gx.nl wrote:
Is it possible to include JCR-2129, JCR-2138 and JCR-2168 in jackrabbit 1.6.0?
Yes, I merged them all to the 1.x
Hi,
On Tue, Jul 7, 2009 at 3:22 PM, Jukka Zittingjukka.zitt...@gmail.com wrote:
I've now changed the JCR project to use the no-reopen-closed,
patch-avail workflow.
I browsed through all our open issues for ones with patches waiting
for action and moved them to the Patch Available state (sorry
Hi Jukka,
I created an issue about a deadlock a few weeks ago.
I was unable to create a Jackrabbit test case but my business test
case always reproduces the deadlock. But, i posted the java stack
trace [1] in order to help finding the race condition.
I know this issue is not fixed yet, but i
Hi,
On Wed, Jul 8, 2009 at 2:39 PM, Sébastien
Launaysebastien.lau...@anyware-tech.com wrote:
I created an issue about a deadlock a few weeks ago.
I was unable to create a Jackrabbit test case but my business test
case always reproduces the deadlock. But, i posted the java stack
trace [1] in
Hi,
On Tue, May 26, 2009 at 3:11 PM, Jukka Zittingjukka.zitt...@gmail.com wrote:
Any objections to changing the workflow? If not, then I'll change the
Jira settings accordingly.
I've now changed the JCR project to use the no-reopen-closed,
patch-avail workflow.
Contributors: When you've
Hi,
Is it possible to include JCR-2129, JCR-2138 and JCR-2168 in jackrabbit 1.6.0?
Best regards,
Martijn Hendriks
-Original Message-
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
Sent: Thursday, June 18, 2009 4:16 PM
To: Jackrabbit Developers
Subject: Re: Jackrabbit 1.6
Hi,
To answer Thomas' comment from JCR-2128, I'm still planning to do the
1.6 release.
The current blocker is finishing up the backup/migration tool I added
some weeks ago (JCR-422). Mostly some extra work is needed in how to
best handle search indexes and the data store.
The reason why I want
Hi,
2009/5/25 Cédric Damioli cedric.dami...@anyware-tech.com:
We provided a patch several months ago, but AFAIK nobody reviewed it.
We've now had already a few cases like this where a perfectly good
patch gets overlooked for months at a time. That's not a a good sign,
so I'd like to find some
+1
greets
claus
This workflow is just like what we have now with two differences:
1) A closed issue can't be reopened. This works well for our Jira
practices, as we normally resolve an issue when it's fixed and
close it when the fix is released. After that the issue should no
longer be
+1
Ian
On 26 May 2009, at 14:11, Jukka Zitting wrote:
Hi,
2009/5/25 Cédric Damioli cedric.dami...@anyware-tech.com:
We provided a patch several months ago, but AFAIK nobody reviewed it.
We've now had already a few cases like this where a perfectly good
patch gets overlooked for months at a
Hi,
On Tue, Apr 21, 2009 at 5:10 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
As noted in various recent threads, we're getting closer to branching
and releasing Jackrabbit 1.6. There are no major blockers to 1.6 so we
should be able to move fairly quickly with the release.
The 1.x branch
Hi Jukka,
Could JCR-134 be part of the 1.6 release ?
We provided a patch several months ago, but AFAIK nobody reviewed it.
This patch is really helpful, as it allows repositories not to grow
unnecessarily over time [1]
There's also a few threads on mailing-lists asking for this feature [2]
Hi,
2009/5/25 Cédric Damioli cedric.dami...@anyware-tech.com:
Could JCR-134 be part of the 1.6 release ?
We provided a patch several months ago, but AFAIK nobody reviewed it.
Sorry about that, I'll give it a look now. Thanks for the heads up.
BR,
Jukka Zitting
Hi,
On Tue, Apr 21, 2009 at 5:10 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Unless anything major comes up, I will create a Jackrabbit 1.x branch
at the end of next week on Friday, April 30th.
That would of course be Thursday, April 30th. I'll never get used to
calendars that start the
Hi,
I like to fix https://issues.apache.org/jira/browse/JCR-2063
(FileDataStore: garbage collection can delete files that are still needed)
Unfortunately, I can't get the data store unit tests to work; the
workspace is closed while the garbage collection is run
('idleTimeout'). I'm not sure if
Hi,
On Tue, Apr 21, 2009 at 6:41 PM, Dan Diephouse
dan.diepho...@mulesource.com wrote:
I'm working on my cleaned up patch for JCR-1659 and a new one for JCR-977.
OK, good to know.
BR,
Jukka Zitting
Hi,
On Wed, Apr 22, 2009 at 9:52 AM, Thomas Müller thomas.muel...@day.com wrote:
I like to fix https://issues.apache.org/jira/browse/JCR-2063
(FileDataStore: garbage collection can delete files that are still needed)
Unfortunately, I can't get the data store unit tests to work; the
workspace
Hi,
Could this be related to JCR-2048?
Yes. Please tell me if you want me to fix this problem.
I propose to include in 1.6:
https://issues.apache.org/jira/browse/JCR-2063
https://issues.apache.org/jira/browse/JCR-2080
Regards,
Thomas
Hi,
As noted in various recent threads, we're getting closer to branching
and releasing Jackrabbit 1.6. There are no major blockers to 1.6 so we
should be able to move fairly quickly with the release. We had some
earlier plans about including a content browser/editor or implementing
database
22 matches
Mail list logo
