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 2006/12/13 12:45:59 UTC
Apache Jackrabbit 1.2 release plan
Hi,
The issue list for the 1.2 release is quickly converging, so here's a
hopefully final update to the release plan. Currently there are only
two open issues (JCR-585 and JCR-670) remaining, and I consider only
JCR-585 a blocker for the release. Other minor fixes might still get
included in the release if time permits.
Since this release contains a number of both structural and functional
changes, I'd like to reserve some time for testing and stabilization
of the codebase before building the release. To achieve this without
blocking development in the svn trunk I'm planning to create the 1.2
branch during next weekend. I will then create one or two candidate
builds from the branch to gather feedback, and proceed with the
official release vote once all potential issues are resolved.
See below for a summary of the planned release. Comments and
suggestions are still welcome. Please speak up now if you still want
some new feature or improvement included in the release. After
branching 1.2 during next weekend I don't plan including anything else
than essential bug fixes in the release.
The Apache Jackrabbit 1.2 release contains a number of improvements
and new features over the previous releases. Most notable changes
include the introduction of a clustering feature and various query
improvements. The build environment has been upgraded to Maven 2 along
with updates to the project structure and new versions of the Apache
Lucene and Apache Derby dependencies. See below for the complete list
of changes:
New Feature
* [JCR-332] - Upgrade to Maven 2
* [JCR-585] - Create jackrabbit-api(.jar) and the respective ...
* [JCR-613] - Implementation of a memory file system
* [JCR-619] - CacheManager (Memory Management in Jackrabbit)
* [JCR-623] - Clustering
* [JCR-638] - Support lower-/upper-case functions
Improvement
* [JCR-247] - Child axis support for XPath predicates
* [JCR-352] - Upgrade to Lucene 2.0
* [JCR-545] - New method on NodeTypeManagerImpl to reregister nodetypes
* [JCR-584] - Improve handling of concurrent node modifications
* [JCR-595] - Refactoring of the Persistence Managers
* [JCR-610] - Upgrade to Derby 10.2
* [JCR-612] - Restructure the Jackrabbit source tree
* [JCR-618] - Replace WeakIdentityCollection in StateChangeDispacher
* [JCR-626] - Move document type definition out of repository.xml
* [JCR-633] - DerbyPersistenceManager only usable for embedded databases
* [JCR-645] - DatabasePersistenceManager & DatabaseFileSystem: try to ...
* [JCR-651] - Improve performance for queries with large result sets
* [JCR-660] - SQL Parser fails with SQL 92 timestamp format
* [JCR-667] - Variant spelling "Trasaction" and "Transaction" now in ...
* [JCR-668] - Allow pseudo properties in query relation
* [JCR-669] - Move NamespaceMappings/Index from lucene to namespace ...
* [JCR-670] - LocalNamespaceMappings does not make use of NameCache ...
Bug
* [JCR-441] - Session logout doesn't release locks acquired using ...
* [JCR-546] - Deadlock during checkin
* [JCR-614] - Weird locking behaviour in CachingHierarchyManager
* [JCR-617] - CachingHieraarchyManager may serve moved items
* [JCR-627] - Deprecated Serializer does not properly delegate method ...
* [JCR-628] - OutOfMemory problem: HandleMonitor does not release ...
* [JCR-632] - VersionManager lock not released in some circumstances
* [JCR-641] - can't add lock token to session after 3 login/logout
* [JCR-648] - NullpointerException in SessionItemStateManager
* [JCR-656] - JCR-Server: Allow header misses colong ...
* [JCR-659] - import of multivalue properties with single value ...
* [JCR-661] - RMIC not working in subprojects when compiling ...
BR,
Jukka Zitting
Re: Apache Jackrabbit 1.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 12/13/06, Jukka Zitting <ju...@gmail.com> wrote:
> Since this release contains a number of both structural and functional
> changes, I'd like to reserve some time for testing and stabilization
> of the codebase before building the release. To achieve this without
> blocking development in the svn trunk I'm planning to create the 1.2
> branch during next weekend.
The 1.2 branch has now been created. I'll make the first release
candidate once there's a resolution to the unit test failure caused by
JCR-529.
BR,
Jukka Zitting
Re: Apache Jackrabbit 1.2 release plan
Posted by Christoph Kiehl <ki...@subshell.com>.
James Hang wrote:
> I assume that the change for JCR-545 only allows reregistering nodetypes with
> trivial modiciations? So it would still throw a RepositoryException("not
> yet implemented") for non-trivial changes?
Yes, you're right.
Cheers,
Chris
Re: Apache Jackrabbit 1.2 release plan
Posted by James Hang <jh...@bea.com>.
I assume that the change for JCR-545 only allows reregistering nodetypes with
trivial modiciations? So it would still throw a RepositoryException("not
yet implemented") for non-trivial changes?
--
View this message in context: http://www.nabble.com/Apache-Jackrabbit-1.2-release-plan-tf2813516.html#a7859068
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
Re: Apache Jackrabbit 1.2 release plan
Posted by Paco Avila <pa...@git.es>.
wonderful news, thanks!
El mié, 13-12-2006 a las 16:50 +0100, Tobias Bocanegra escribió:
> i just committed the suggested patch from paco.
> regards, toby
>
> On 12/13/06, Jukka Zitting <ju...@gmail.com> wrote:
> > Hi,
> >
> > On 12/13/06, Paco Avila <pa...@git.es> wrote:
> > > What about issue JCR-529?
> >
> > Seems good. I'm not too familiar with the details of version naming
> > and the possible implications of changing things, so Tobias can
> > probably better decide whether the change is good for inclusion in
> > 1.2.
> >
> > BR,
> >
> > Jukka Zitting
> >
>
>
--
GIT Consultors S.L.
c\ Francesc Rover 2-B
07003 Palma de Mallorca
(Illes Balears)
Re: Apache Jackrabbit 1.2 release plan
Posted by Tobias Bocanegra <to...@day.com>.
i just committed the suggested patch from paco.
regards, toby
On 12/13/06, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On 12/13/06, Paco Avila <pa...@git.es> wrote:
> > What about issue JCR-529?
>
> Seems good. I'm not too familiar with the details of version naming
> and the possible implications of changing things, so Tobias can
> probably better decide whether the change is good for inclusion in
> 1.2.
>
> BR,
>
> Jukka Zitting
>
--
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---
Re: Apache Jackrabbit 1.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 12/13/06, Paco Avila <pa...@git.es> wrote:
> What about issue JCR-529?
Seems good. I'm not too familiar with the details of version naming
and the possible implications of changing things, so Tobias can
probably better decide whether the change is good for inclusion in
1.2.
BR,
Jukka Zitting
Re: Apache Jackrabbit 1.2 release plan
Posted by Paco Avila <pa...@git.es>.
What about issue JCR-529?
--
GIT Consultors S.L.
c\ Francesc Rover 2-B
07003 Palma de Mallorca
(Illes Balears)
Re: Apache Jackrabbit 1.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 12/13/06, Przemo Pakulski <pr...@cognifide.com> wrote:
> I'm mostly concerned about JCR-546.
>
> It seems that proposed patch does not resolve the problem, because it
> breaks order of acquired locks (see JCR-632),
You mean JCR-672? As I just commented on the issue, I don't think the
problems are related. JCR-546 can mostly have enlarged the window of
opportunity for this deadlock to occur by extending the scope of the
write lock.
It would be very nice to have a fix also for JCR-672 included in
Jackrabbit 1.2, but I'm not making it a blocker since it's still not
the only open issue on concurrent versioning operations (JCR-18 being
the core known issue).
> In long term it seems that all usage of locks needs to be identified and
> reviewed again.
Agreed.
BR,
Jukka Zitting
Re: Apache Jackrabbit 1.2 release plan
Posted by Przemo Pakulski <pr...@cognifide.com>.
Hi,
I'm mostly concerned about JCR-546.
It seems that proposed patch does not resolve the problem, because it
breaks order of acquired locks (see JCR-632),
If there is no other quick solution possible, I suggest to:
1. Revert patch changes,
2. Make fix to ugrade read lock to write lock correclty (as suggested by
Rod)
3. Then fix JCR-632 to make sure lock is always released.
I can provide a patch for this, then I can make some concurrent tests to
check this, I think.
In long term it seems that all usage of locks needs to be identified and
reviewed again.
Przemo
> Hi,
>
> The issue list for the 1.2 release is quickly converging, so here's a
> hopefully final update to the release plan. Currently there are only
> two open issues (JCR-585 and JCR-670) remaining, and I consider only
> JCR-585 a blocker for the release. Other minor fixes might still get
> included in the release if time permits.
>
> Since this release contains a number of both structural and functional
> changes, I'd like to reserve some time for testing and stabilization
> of the codebase before building the release. To achieve this without
> blocking development in the svn trunk I'm planning to create the 1.2
> branch during next weekend. I will then create one or two candidate
> builds from the branch to gather feedback, and proceed with the
> official release vote once all potential issues are resolved.
>
> See below for a summary of the planned release. Comments and
> suggestions are still welcome. Please speak up now if you still want
> some new feature or improvement included in the release. After
> branching 1.2 during next weekend I don't plan including anything else
> than essential bug fixes in the release.
>
> The Apache Jackrabbit 1.2 release contains a number of improvements
> and new features over the previous releases. Most notable changes
> include the introduction of a clustering feature and various query
> improvements. The build environment has been upgraded to Maven 2 along
> with updates to the project structure and new versions of the Apache
> Lucene and Apache Derby dependencies. See below for the complete list
> of changes:
>
> New Feature
>
> * [JCR-332] - Upgrade to Maven 2
> * [JCR-585] - Create jackrabbit-api(.jar) and the respective ...
> * [JCR-613] - Implementation of a memory file system
> * [JCR-619] - CacheManager (Memory Management in Jackrabbit)
> * [JCR-623] - Clustering
> * [JCR-638] - Support lower-/upper-case functions
>
> Improvement
>
> * [JCR-247] - Child axis support for XPath predicates
> * [JCR-352] - Upgrade to Lucene 2.0
> * [JCR-545] - New method on NodeTypeManagerImpl to reregister nodetypes
> * [JCR-584] - Improve handling of concurrent node modifications
> * [JCR-595] - Refactoring of the Persistence Managers
> * [JCR-610] - Upgrade to Derby 10.2
> * [JCR-612] - Restructure the Jackrabbit source tree
> * [JCR-618] - Replace WeakIdentityCollection in StateChangeDispacher
> * [JCR-626] - Move document type definition out of repository.xml
> * [JCR-633] - DerbyPersistenceManager only usable for embedded databases
> * [JCR-645] - DatabasePersistenceManager & DatabaseFileSystem: try to
> ...
> * [JCR-651] - Improve performance for queries with large result sets
> * [JCR-660] - SQL Parser fails with SQL 92 timestamp format
> * [JCR-667] - Variant spelling "Trasaction" and "Transaction" now in ...
> * [JCR-668] - Allow pseudo properties in query relation
> * [JCR-669] - Move NamespaceMappings/Index from lucene to namespace ...
> * [JCR-670] - LocalNamespaceMappings does not make use of NameCache ...
>
> Bug
>
> * [JCR-441] - Session logout doesn't release locks acquired using ...
> * [JCR-546] - Deadlock during checkin
> * [JCR-614] - Weird locking behaviour in CachingHierarchyManager
> * [JCR-617] - CachingHieraarchyManager may serve moved items
> * [JCR-627] - Deprecated Serializer does not properly delegate method
> ...
> * [JCR-628] - OutOfMemory problem: HandleMonitor does not release ...
> * [JCR-632] - VersionManager lock not released in some circumstances
> * [JCR-641] - can't add lock token to session after 3 login/logout
> * [JCR-648] - NullpointerException in SessionItemStateManager
> * [JCR-656] - JCR-Server: Allow header misses colong ...
> * [JCR-659] - import of multivalue properties with single value ...
> * [JCR-661] - RMIC not working in subprojects when compiling ...
>
> BR,
>
> Jukka Zitting