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 2008/02/21 19:08:22 UTC
jackrabbit-core 1.4.2 release plan
Hi,
At Day we are also hitting the JCR-1359 issue [1] in certain cases,
and it seems like I'll be spending some more time looking at the
issue. Once resolved, I'd like to make a new 1.4.x patch release
containing the JCR-1359 fix.
At the moment there are no other 1.4 issues that would be candidates
for inclusion in jackrabbit-core 1.4.2, but feel free to tag issues
with the "core 1.4.2" Fix Version if there are fixes you'd like to see
included in this release.
[1] https://issues.apache.org/jira/browse/JCR-1359
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Feb 21, 2008 at 9:57 PM, Alex Lukin <lu...@stu.cn.ua> wrote:
> Thursday 21 February 2008 21:40:09 Jukka Zitting написав:
> > Our policy has normally been to only include bug fixes in patch
> > releases, so I'd rather wait for 1.5 until releasing JCR-1365.
>
> Is it bug fix: significant (10x times) speedup of terrible sluggish query?
No. A bug is a deviation from documented behaviour.
We haven't documented the kind of query performance you can expect, so
a performance improvement clearly isn't a bug fix.
> This patch does not change behavior or adds new feature.
You're right, but it's still a non-trivial code change that might well
introduce unknown regressions. It is good practice to avoid
introducing unnecessary changes in maintenance branches.
> Please, find a way to include it in 1.4.2 if it is possiibe.
The change belongs in the 1.5 release, but there's no stopping us from
releasing Jackrabbit 1.5 already next week if we so decide. Personally
I don't think JCR-1365 is by itself important enough to justify a new
release and people who want or need it immediately can just as well
build the current trunk for themselves, but if there are enough people
who'd like to see 1.5 released soon then I don't see any reason why we
couldn't do that.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.2 release plan
Posted by Alex Lukin <lu...@stu.cn.ua>.
Thursday 21 February 2008 21:40:09 Jukka Zitting написав:
>
> Our policy has normally been to only include bug fixes in patch
> releases, so I'd rather wait for 1.5 until releasing JCR-1365.
>
Is it bug fix: significant (10x times) speedup of terrible sluggish query? This patch does not change behavior or adds new feature.
Please, find a way to include it in 1.4.2 if it is possiibe.
--
SY, Alex Lukin
RIPE NIC HDL: LEXA1-RIPE
Re: jackrabbit-core 1.4.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Feb 21, 2008 at 8:50 PM, Alex Lukin <lu...@stu.cn.ua> wrote:
> I tested resolved issue 1365 (xpath query speedup) and it works perfect.
> It marked for 1.5 release but IMO not depends on other changes.
> Could you please include this solution in 1.4.2?
Our policy has normally been to only include bug fixes in patch
releases, so I'd rather wait for 1.5 until releasing JCR-1365.
My current thinking puts Jackrabbit 1.5 on a pretty aggressive
schedule to be released already in a few months. I'll follow up with
an initial release plan in the next few days.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.2 release plan
Posted by Alex Lukin <lu...@stu.cn.ua>.
Hi, Jukka!
I tested resolved issue 1365 (xpath query speedup) and it works perfect.
It marked for 1.5 release but IMO not depends on other changes.
Could you please include this solution in 1.4.2?
--
SY, Alex Lukin
RIPE NIC HDL: LEXA1-RIPE
Re: jackrabbit-core 1.4.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Feb 22, 2008 at 12:20 PM, Marcel Reutegger
<ma...@gmx.net> wrote:
> I'd like to include the fix for JCR-1408 in 1.4.2.
>
> If that's OK with you, I will merge the changes into the 1.4 branch.
Yes, that would be great.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.2 release plan
Posted by Marcel Reutegger <ma...@gmx.net>.
Jukka Zitting wrote:
> At the moment there are no other 1.4 issues that would be candidates
> for inclusion in jackrabbit-core 1.4.2, but feel free to tag issues
> with the "core 1.4.2" Fix Version if there are fixes you'd like to see
> included in this release.
I'd like to include the fix for JCR-1408 in 1.4.2.
If that's OK with you, I will merge the changes into the 1.4 branch.
regards
marcel
Re: jackrabbit-core 1.4.2 release plan
Posted by Tobias Bocanegra <to...@day.com>.
sorry i was wrong - i just checked the 1.3 code which already had this issue.
so i don't care if it's included in 1.4.2 or not.
On 3/13/08, Tobias Bocanegra <to...@day.com> wrote:
> i would also add
> [JCR-1471] Error when registering nodetype with same propdef as supertype
>
> since it breaks existing custom nodetype def imports. i have not
> verified it, but i assume it was introduced with the SPI abstraction.
>
> regards, toby
>
> On 3/13/08, Jukka Zitting <ju...@gmail.com> wrote:
> > Hi,
> >
> > We now have JCR-1359 and a number of other jackrabbit-core issues
> > fixed, and I'm ready to tag and build a candidate for the 1.4.2
> > release. The current list of changes in this release is:
> >
> > Improvements
> > [JCR-1375] Limit fields read from index
> >
> > Bug fixes
> > [JCR-1275] NullPointerException in AbstractVersionManager....
> > [JCR-1359] Adding nodes from concurrently running sessions cause exceptions
> > [JCR-1414] Data store garbage collection: inUse not correctly synchronized
> > [JCR-1408] Invalid query results when using jcr:like with a case ...
> > [JCR-1459] NullPointerException on startup if IndexingQueue has ...
> > [JCR-1449] Registering nodetypes with empty namespace prefix causes ...
> > [JCR-1427] XPath query with child axis predicates
> > [JCR-1453] Allow access to journal inside ClusterNode
> > [JCR-1415] Clustering configuration documentation for syncDelay ...
> > [JCR-1432] Saving a node deletion that has been modified externally ...
> > [JCR-1460] Typo in repository.xml
> >
> > I'm not convinced that JCR-1375 should be in this patch release, and
> > there is also demand to have JCR-1469 included.
> >
> > I'd personally like to keep a hard line on release versioning, i.e.
> > only bug fixes in patch releases and if needed do more frequent minor
> > releases for other improvements and new features.
> >
> > WDYT, should we be more relaxed in what goes into each release, or
> > should we keep up the strict release policy? In the latter case I
> > think we should go further down the line of component releases and
> > allow releases like jackrabbit-core 1.5 whenever needed regardless of
> > the status of other components.
> >
> > 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 >---
>
--
-----------------------------------------< 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: jackrabbit-core 1.4.2 release plan
Posted by Tobias Bocanegra <to...@day.com>.
i would also add
[JCR-1471] Error when registering nodetype with same propdef as supertype
since it breaks existing custom nodetype def imports. i have not
verified it, but i assume it was introduced with the SPI abstraction.
regards, toby
On 3/13/08, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> We now have JCR-1359 and a number of other jackrabbit-core issues
> fixed, and I'm ready to tag and build a candidate for the 1.4.2
> release. The current list of changes in this release is:
>
> Improvements
> [JCR-1375] Limit fields read from index
>
> Bug fixes
> [JCR-1275] NullPointerException in AbstractVersionManager....
> [JCR-1359] Adding nodes from concurrently running sessions cause exceptions
> [JCR-1414] Data store garbage collection: inUse not correctly synchronized
> [JCR-1408] Invalid query results when using jcr:like with a case ...
> [JCR-1459] NullPointerException on startup if IndexingQueue has ...
> [JCR-1449] Registering nodetypes with empty namespace prefix causes ...
> [JCR-1427] XPath query with child axis predicates
> [JCR-1453] Allow access to journal inside ClusterNode
> [JCR-1415] Clustering configuration documentation for syncDelay ...
> [JCR-1432] Saving a node deletion that has been modified externally ...
> [JCR-1460] Typo in repository.xml
>
> I'm not convinced that JCR-1375 should be in this patch release, and
> there is also demand to have JCR-1469 included.
>
> I'd personally like to keep a hard line on release versioning, i.e.
> only bug fixes in patch releases and if needed do more frequent minor
> releases for other improvements and new features.
>
> WDYT, should we be more relaxed in what goes into each release, or
> should we keep up the strict release policy? In the latter case I
> think we should go further down the line of component releases and
> allow releases like jackrabbit-core 1.5 whenever needed regardless of
> the status of other components.
>
> 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: jackrabbit-core 1.4.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Mar 14, 2008 at 11:28 AM, Marcel Reutegger
<ma...@gmx.net> wrote:
> please see my comment in JCR-1375.
Good enough for me, let's keep the change in 1.4.2.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.2 release plan
Posted by Marcel Reutegger <ma...@gmx.net>.
Esteban Franqueiro wrote:
>> I'm not convinced that JCR-1375 should be in this patch release, and
>> there is also demand to have JCR-1469 included.
>
> I agree with Jukka regarding JCR-1375.
please see my comment in JCR-1375.
regards
marcel
Re: jackrabbit-core 1.4.2 release plan
Posted by Esteban Franqueiro <es...@bea.com>.
> I'm not convinced that JCR-1375 should be in this patch release, and
> there is also demand to have JCR-1469 included.
I agree with Jukka regarding JCR-1375.
> I'd personally like to keep a hard line on release versioning, i.e.
> only bug fixes in patch releases and if needed do more frequent minor
> releases for other improvements and new features.
Also agree on this one, so JCR-1469 should go 1.4.2.
> WDYT, should we be more relaxed in what goes into each release, or
> should we keep up the strict release policy? In the latter case I
> think we should go further down the line of component releases and
> allow releases like jackrabbit-core 1.5 whenever needed regardless of
> the status of other components.
In general I think that we should be strict about this, but I also think that if a particular issue
is urgent, it could be included in a patch release if most people want to.
But strict decisions can only be made after a policy is in place. In our case, I'm not sure if
there's consensus about our release policy.
My AR$0,02.
All in all, I agree with this proposal for Jackrabbit 1.4.2.
Regards,
Esteban Franqueiro
esteban.franqueiro@bea.com
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Re: jackrabbit-core 1.4.2 release plan
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
Am Donnerstag, den 13.03.2008, 16:17 +0200 schrieb Jukka Zitting:
> I'd personally like to keep a hard line on release versioning, i.e.
> only bug fixes in patch releases and if needed do more frequent minor
> releases for other improvements and new features.
I can live with both solutions. What is paramount to me, is that we can
get more frequent releaes of components. I would even go a step further
and say, that sometimes it makes sense to create a release even in the
case of enhancements.
Whatever we do: version numbers of components will diverge and we should
not fall into the trap of raising all version numbers to the same
numbers just because of a minor release. This would really be
problematic to dependency management - as I always said ;-)
>
> WDYT, should we be more relaxed in what goes into each release, or
> should we keep up the strict release policy? In the latter case I
> think we should go further down the line of component releases and
> allow releases like jackrabbit-core 1.5 whenever needed regardless of
> the status of other components.
Once consequence we should certainly not get out of sight: Currently the
parent pom not only manages dependencies external to Jackrabbit - such
as lucene - but also internal dependencies between different components
of Jackrabbit.
Likewise, each component just inherits the version number of the parent
pom.
Both of these setups will have to be changed no matter what: Each
component defines its own version number, which is always a SNAPSHOT
version number - except for tagged versions - and dependencies between
components are always set to the minimal released number of the
depending component. This way we can also better managed release
dependencies.
If we just raise the dependencies between Jackrabbit Components each
time a release happens, this amounts to a nightmare of not being able to
track the actual dependency requirement !
Regards
Felix
Re: jackrabbit-core 1.4.2 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
We now have JCR-1359 and a number of other jackrabbit-core issues
fixed, and I'm ready to tag and build a candidate for the 1.4.2
release. The current list of changes in this release is:
Improvements
[JCR-1375] Limit fields read from index
Bug fixes
[JCR-1275] NullPointerException in AbstractVersionManager....
[JCR-1359] Adding nodes from concurrently running sessions cause exceptions
[JCR-1414] Data store garbage collection: inUse not correctly synchronized
[JCR-1408] Invalid query results when using jcr:like with a case ...
[JCR-1459] NullPointerException on startup if IndexingQueue has ...
[JCR-1449] Registering nodetypes with empty namespace prefix causes ...
[JCR-1427] XPath query with child axis predicates
[JCR-1453] Allow access to journal inside ClusterNode
[JCR-1415] Clustering configuration documentation for syncDelay ...
[JCR-1432] Saving a node deletion that has been modified externally ...
[JCR-1460] Typo in repository.xml
I'm not convinced that JCR-1375 should be in this patch release, and
there is also demand to have JCR-1469 included.
I'd personally like to keep a hard line on release versioning, i.e.
only bug fixes in patch releases and if needed do more frequent minor
releases for other improvements and new features.
WDYT, should we be more relaxed in what goes into each release, or
should we keep up the strict release policy? In the latter case I
think we should go further down the line of component releases and
allow releases like jackrabbit-core 1.5 whenever needed regardless of
the status of other components.
BR,
Jukka Zitting