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 2009/04/01 10:11:36 UTC

Re: Jackrabbit 1.5.5 release plan

Hi,

On Thu, Mar 12, 2009 at 3:27 PM, Martijn Hendriks <ma...@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

Re: Jackrabbit 1.5.5 release plan

Posted by Frank van Lankvelt <f....@onehippo.com>.
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 <ju...@gmail.com>wrote:

> Hi,
>
> On Tue, Apr 21, 2009 at 12:31 PM, Frank van Lankvelt
> <f....@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

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Tue, Apr 21, 2009 at 12:31 PM, Frank van Lankvelt
<f....@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

Posted by Frank van Lankvelt <f....@onehippo.com>.
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 <ju...@gmail.com>wrote:

> Hi,
>
> On Wed, Apr 1, 2009 at 10:11 AM, Jukka Zitting <ju...@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

Posted by Michael Dürig <mi...@day.com>.
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

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Tue, Apr 21, 2009 at 12:07 PM, Jukka Zitting <ju...@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

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Wed, Apr 1, 2009 at 10:11 AM, Jukka Zitting <ju...@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