Re: Jackrabbit 1.5.5 release plan

2009-04-23 Thread Jukka Zitting
Hi, On Tue, Apr 21, 2009 at 12:07 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: I'm just reviewing the last pending commits in trunk. Michael is still looking at some SPI fixes to be included in 1.5.5, and I plan to cut the release as soon as those issues are sorted out. Pretty much all

Re: Jackrabbit 1.5.5 release plan

2009-04-23 Thread Michael Dürig
Jukka Zitting wrote: JCR-2070 is still open, but I'm not sure if we should include it in 1.5.5. Michael's second patch looks nice, but perhaps it's better to schedule it for 1.5.6? That's fine with me. The fix is less urgent than I initially thought. Michael Unless anyone objects,

Re: Jackrabbit 1.5.5 release plan

2009-04-22 Thread Michael Dürig
Hi, I'd like to have https://issues.apache.org/jira/browse/JCR-2070 fixed for 1.5.5. Are there any objections? If not I would apply the patch attached to the issue. Michael Jukka Zitting wrote: Hi, On Thu, Mar 12, 2009 at 12:07 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Any

Re: Jackrabbit 1.5.5 release plan

2009-04-21 Thread Jukka Zitting
Hi, On Wed, Apr 1, 2009 at 10:11 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: More generally, with the 1.5.4 release candidate tagged and out for review, I'm moving forward with the 1.5.5 release. I'm just reviewing the last pending commits in trunk. Michael is still looking at some SPI

Re: Jackrabbit 1.5.5 release plan

2009-04-21 Thread Frank van Lankvelt
Hi Jukka, could issue JCR-2016 (jcr2spi) be considered for inclusion? There is a patch attached that fixes some faults in the update processing. I.e. a correct update leads to an incorrect state. thanks, Frank On Tue, Apr 21, 2009 at 12:07 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi,

Re: Jackrabbit 1.5.5 release plan

2009-04-21 Thread Jukka Zitting
Hi, On Tue, Apr 21, 2009 at 12:31 PM, Frank van Lankvelt f.vanlankv...@onehippo.com wrote: could issue JCR-2016 (jcr2spi) be considered for inclusion?  There is a patch attached that fixes some faults in the update processing.  I.e. a correct update leads to an incorrect state. Sure, sorry

Re: Jackrabbit 1.5.5 release plan

2009-04-21 Thread Frank van Lankvelt
thanks for reviewing! Sorry about the absense of a test, I'll have to look into how to do that. I guess it should be possible by creating a mock repository service to fabricate the updates(?) Frank On Tue, Apr 21, 2009 at 6:00 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Tue, Apr

Re: Jackrabbit 1.5.5 release plan

2009-04-01 Thread Jukka Zitting
Hi, On Thu, Mar 12, 2009 at 3:27 PM, Martijn Hendriks marti...@gx.nl wrote: It would be nice if JCR-1117 could be part of 1.5.5. Agreed. I merged the fix to the 1.5 branch. More generally, with the 1.5.4 release candidate tagged and out for review, I'm moving forward with the 1.5.5 release. A

Jackrabbit 1.5.5 release plan

2009-03-12 Thread Jukka Zitting
Hi, On Thu, Mar 12, 2009 at 12:07 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Any other changes should wait for 1.5.5. Since we already have a few candidates like JCR-1216, I think we should do the 1.5.5 release in near future. In preparation for the release I've now created the 1.5.5 tag

RE: Jackrabbit 1.5.5 release plan

2009-03-12 Thread Martijn Hendriks
Hi Jukka, It would be nice if JCR-1117 could be part of 1.5.5. Best regards, Martijn -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, March 12, 2009 12:16 PM To: Jackrabbit Developers Subject: Jackrabbit 1.5.5 release plan Hi, On Thu