Jackrabbit 1.5.4 release plan (Was: [VOTE] Release Apache Jackrabbit 1.5.3)

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Feb 26, 2009 at 10:42 AM, Jukka Zitting <ju...@gmail.com> wrote:
> PS. Note that there was another deadlock case detected in relation to
> the JCR-1979 fix. But since the original JCR-1979 bug is still fixed
> it's good to push the 1.5.3 release out as it is. I'll be posting a
> 1.5.4 release candidate next week as soon as I've got a fix to the
> follow-up issue JCR-2000.

As mentioned above, I'm planning to do a 1.5.4 release next week. The
driving issue for the release is JCR-2000, but let me know if you have
other fixes in mind that didn't make it in 1.5.3 and should be
released.

However, I'd like to only include minimum risk fixes in 1.5.4 as 1.5.3
was quite heavily tested and I don't want to invalidate those tests
for 1.5.4 by making too many changes. We can do a 1.5.5 later if there
are bigger fixes to be included.

BR,

Jukka Zitting

Re: Jackrabbit 1.5.4 release plan (Was: [VOTE] Release Apache Jackrabbit 1.5.3)

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Feb 26, 2009 at 11:13 AM, Jukka Zitting <ju...@gmail.com> wrote:
> However, I'd like to only include minimum risk fixes in 1.5.4 as 1.5.3
> was quite heavily tested and I don't want to invalidate those tests
> for 1.5.4 by making too many changes.

Just to keep everyone on the same page, the 1.5.4 release is now
scheduled to contain the following related fixes:

  [JCR-2000] Deadlock on concurrent commits
  [JCR-2008] System search manager uses a SessionItemStateManager

Any other changes should wait for 1.5.5.

Przemo is still running tests on the 1.5 branch, and once he's happy
with the results I'll cut the 1.5.4 candidate and start the release
vote.

BR,

Jukka Zitting