Re: Jackrabbit 1.5.5 release plan
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 the relevant fixes are now in the 1.5 branch. See below for the full list of bug fixes and improvements (for jcr2spi) to be included in the 1.5.5 release. 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? Unless anyone objects, I'll cut the release in the evening today. jackrabbit-jcr-commons Bug fixes [JCR-1976] Text.unescape() should should preserve 'unicode' characters [JCR-1996] Handle date values in the far future or prevent these from ... [JCR-1997] Performance fix, when deserializing large jcr:binary in ... [JCR-2017] System view export truncates carriage return jackrabbit-core Bug fixes [JCR-1117] Bundle cache is not rolled back when the storage of a ... [JCR-1216] Unreferenced sessions should get garbage collected [JCR-1996] Handle date values in the far future or prevent these from ... [JCR-2007] Importing strings with special characters fails [JCR-2020] Overlapping index aggregates not updated [JCR-2035] IndexingQueue not checked on initial index creation [JCR-2048] Workspace is shut down while creating initial index [JCR-2036] Set_property permission not checked when saving a new node [JCR-2057] When creating multiple repository instances pointing to the ... [JCR-2063] FileDataStore: garbage collection can delete files that are ... [JCR-2071] IndexMerger throws null pointer exception without stacktrace [JCR-2080] DataStore: garbage collection can fail when using workspace ... jackrabbit-webdav Bug fixes [JCR-2009] Large file download over webdav causes exception jackrabbit-spi-commons Bug fixes [JCR-2052] XPath QueryFormat may produce malformed XPath statement jackrabbit-jcr2spi Bug fixes [JCR-1886] jcr2spi: Unprocessed ItemInfos call to RepositoryService#... [JCR-2014] Jcr2Spi: Warning upon reloading property values [JCR-2016] ChildNodeEntriesImpl.update logs incorrect errors Improvements [JCR-1870] jcr2spi: reloading of invalidated nodes doesn't benefit from ... [JCR-1871] jcr2spi: use jcr names and path for log and exception message [JCR-1891] jcr2spi: use Soft refs for hierarchy [JCR-1906] Make observation polling time configurable [JCR-1963] Determination of property state difference should skip binary ... [JCR-1966] [PATCH] Remove Stutter in NodeState [JCR-1967] Impossible comparison in NodeTypeImpl [JCR-2038] Lower log level in o.a.j.jcr2spi.query.NodeIteratorImpl [JCR-2039] Add log information when node/property type determination fails BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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, I'll cut the release in the evening today. jackrabbit-jcr-commons Bug fixes [JCR-1976] Text.unescape() should should preserve 'unicode' characters [JCR-1996] Handle date values in the far future or prevent these from ... [JCR-1997] Performance fix, when deserializing large jcr:binary in ... [JCR-2017] System view export truncates carriage return jackrabbit-core Bug fixes [JCR-1117] Bundle cache is not rolled back when the storage of a ... [JCR-1216] Unreferenced sessions should get garbage collected [JCR-1996] Handle date values in the far future or prevent these from ... [JCR-2007] Importing strings with special characters fails [JCR-2020] Overlapping index aggregates not updated [JCR-2035] IndexingQueue not checked on initial index creation [JCR-2048] Workspace is shut down while creating initial index [JCR-2036] Set_property permission not checked when saving a new node [JCR-2057] When creating multiple repository instances pointing to the ... [JCR-2063] FileDataStore: garbage collection can delete files that are ... [JCR-2071] IndexMerger throws null pointer exception without stacktrace [JCR-2080] DataStore: garbage collection can fail when using workspace ... jackrabbit-webdav Bug fixes [JCR-2009] Large file download over webdav causes exception jackrabbit-spi-commons Bug fixes [JCR-2052] XPath QueryFormat may produce malformed XPath statement jackrabbit-jcr2spi Bug fixes [JCR-1886] jcr2spi: Unprocessed ItemInfos call to RepositoryService#... [JCR-2014] Jcr2Spi: Warning upon reloading property values [JCR-2016] ChildNodeEntriesImpl.update logs incorrect errors Improvements [JCR-1870] jcr2spi: reloading of invalidated nodes doesn't benefit from ... [JCR-1871] jcr2spi: use jcr names and path for log and exception message [JCR-1891] jcr2spi: use Soft refs for hierarchy [JCR-1906] Make observation polling time configurable [JCR-1963] Determination of property state difference should skip binary ... [JCR-1966] [PATCH] Remove Stutter in NodeState [JCR-1967] Impossible comparison in NodeTypeImpl [JCR-2038] Lower log level in o.a.j.jcr2spi.query.NodeIteratorImpl [JCR-2039] Add log information when node/property type determination fails BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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 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 in Jira. Feel free to use it for tagging any reasonably safe bug fixes you'd like to see backported from the trunk. Unless anyone has a pressing need for this, I will do the release in early April after the ApacheCon. At around that time we should probably also start thinking about a 1.6 release. BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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 fixes to be included in 1.5.5, and I plan to cut the release as soon as those issues are sorted out. BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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, 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 fixes to be included in 1.5.5, and I plan to cut the release as soon as those issues are sorted out. BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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 that nobody has commented on the patch yet. (Perhaps we should start using the patch available workflow in Jira...) The patch looks reasonably OK, though I'd need to review it in a bit more detail before applying it. Any chance of getting a test case for it? :-) BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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 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 that nobody has commented on the patch yet. (Perhaps we should start using the patch available workflow in Jira...) The patch looks reasonably OK, though I'd need to review it in a bit more detail before applying it. Any chance of getting a test case for it? :-) BR, Jukka Zitting
Re: Jackrabbit 1.5.5 release plan
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 release candidate can be expected within a week or two. BR, Jukka Zitting
Jackrabbit 1.5.5 release plan
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 in Jira. Feel free to use it for tagging any reasonably safe bug fixes you'd like to see backported from the trunk. Unless anyone has a pressing need for this, I will do the release in early April after the ApacheCon. At around that time we should probably also start thinking about a 1.6 release. BR, Jukka Zitting
RE: Jackrabbit 1.5.5 release plan
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, 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 in Jira. Feel free to use it for tagging any reasonably safe bug fixes you'd like to see backported from the trunk. Unless anyone has a pressing need for this, I will do the release in early April after the ApacheCon. At around that time we should probably also start thinking about a 1.6 release. BR, Jukka Zitting
