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/03/07 08:57:27 UTC
Jackrabbit 1.0 branched
Hi,
A bit later than originally planned, I've now created the 1.0 branch
and postponed a number of remaining issues to 1.1 as described in the
Jackrabbit 1.0 release plan. Please let me know if you still want to
have some changes included in 1.0.
The branch seems to be in a pretty good shape by default and the
remaining 1.0 issue (JCR-156) doesn't suggest any explicit changes, so
I will make the first release candidate already in the evening.
Comments on the issues declared critical in the Jackrabbit 1.0 release plan:
[JCR-156] Review test cases and cross check with 1.0 specification
This is the only remaining 1.0 issue after the postponing of other
open issues. Marcel, can we declare this resolved, or do you want to
keep it as a meta-issue?
[JCR-215] Code depends on Log4J directly
Based on previous email discussions I had hoped for SLF4J 1.0 to be
released already now. This is however not the case, so in the interest
of avoiding unknown delays I decided to postpone this issue even
though I declared it critical in the release plan.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/9/06, Angela Schreiber <an...@day.com> wrote:
> don't get me wrong, i don't feel uneasy about it. i simply
> was not aware that the jcr-server was planned for being included
> in the final release before your mail suggesting to move it out
> of the contrib section and therefore did not feel any time pressure
> for removing the dependency mentioned in JCR 337.
OK, good to know.
> however, as mentioned before, i'm done with that in the mean time and
> will commit the changes as soon as possible. just let me make
> sure, i didn't break things.
Thanks. There's no immediate time pressure as I'll wait for graduation
from the Incubator before releasing 1.0. But it would be nice if you
could get the change tested and committed by the end of next week.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by Angela Schreiber <an...@day.com>.
hi jukka
> I didn't have jcr-server in the 0.9 release to keep it simple, but I
> did mention having jcr-server included already in the first draft of
> the 1.0 release plan. I'm sorry for not making more noise about that.
> If you are uneasy about including jcr-server in the release then I can
> drop it for now.
don't get me wrong, i don't feel uneasy about it. i simply
was not aware that the jcr-server was planned for being included
in the final release before your mail suggesting to move it out
of the contrib section and therefore did not feel any time pressure
for removing the dependency mentioned in JCR 337.
however, as mentioned before, i'm done with that in the mean time and
will commit the changes as soon as possible. just let me make
sure, i didn't break things.
kind regards
angela
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/9/06, Angela Schreiber <an...@day.com> wrote:
> > I don't expect to have too many changes in the 1.0 branch so apply
> > your judgement on whether an issue is important and low-risk enough to
> > be included in 1.0. We'll always have 1.1 for more improvements. :-)
>
> right. but i'd like to limit api changes between 1.0 and 1.1
> if possible.
Agreed. The API change scores high enough on the importancy scale to
warrant inclusion in 1.0.
> i knew about JCR-337 for some time before, but
> since the jcr-server contrib was not part of the original release
> plan i didn't feel any hurry for this.
>
> it's fine by me to include the jcr-server contrib in the
> 1.0 release but i feel there is the need for this change
> before the release. i'm sorry if that is cumbersome for you
> as release manager and move the release date. on the other hand
> i was a bit surprised, that all in a sudden the contribs
> were included in the release.
I didn't have jcr-server in the 0.9 release to keep it simple, but I
did mention having jcr-server included already in the first draft of
the 1.0 release plan. I'm sorry for not making more noise about that.
If you are uneasy about including jcr-server in the release then I can
drop it for now.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by Angela Schreiber <an...@day.com>.
hi jukka
> As a general rule for getting fixes into the 1.0 branch; if you have a
> fix for an important enough issue that you'd like to still have
> included in the 1.0 release, do this:
thanks for the instruction
> I don't expect to have too many changes in the 1.0 branch so apply
> your judgement on whether an issue is important and low-risk enough to
> be included in 1.0. We'll always have 1.1 for more improvements. :-)
right. but i'd like to limit api changes between 1.0 and 1.1
if possible. i knew about JCR-337 for some time before, but
since the jcr-server contrib was not part of the original release
plan i didn't feel any hurry for this.
it's fine by me to include the jcr-server contrib in the
1.0 release but i feel there is the need for this change
before the release. i'm sorry if that is cumbersome for you
as release manager and move the release date. on the other hand
i was a bit surprised, that all in a sudden the contribs
were included in the release.
thanks for you understanding
angela
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/9/06, Angela Schreiber <an...@day.com> wrote:
> i'd like to have the jcr dependency removed in
> the webdav library for 1.0.
> actually i'm already done, but i'd like to run
> some tests before i commit the changes.
OK, this shouldn't be a problem.
As a general rule for getting fixes into the 1.0 branch; if you have a
fix for an important enough issue that you'd like to still have
included in the 1.0 release, do this:
1) Have the issue filed in Jira
2) Have the JCR-nnn issue tag included in all related commit messages
3) Include only changes related to that issue in the commits you make
4) Test the fix for any regressions before resolving the issue
5) Set the fix version to 1.0 when resolving the issue and comment
that you'd like the it included in the 1.0 branch
6) I'll merge the changes to the branch.
I don't expect to have too many changes in the 1.0 branch so apply
your judgement on whether an issue is important and low-risk enough to
be included in 1.0. We'll always have 1.1 for more improvements. :-)
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by Angela Schreiber <an...@day.com>.
hi jukka
Jukka Zitting wrote:
> Please let me know if you still want to
> have some changes included in 1.0.
i'd like to have the jcr dependency removed in
the webdav library for 1.0.
actually i'm already done, but i'd like to run
some tests before i commit the changes.
kind regards
angela
https://issues.apache.org/jira/browse/JCR-337
Re: Jackrabbit 1.0 branched
Posted by Marcel Reutegger <ma...@gmx.net>.
Jukka Zitting wrote:
> [JCR-156] Review test cases and cross check with 1.0 specification
>
> This is the only remaining 1.0 issue after the postponing of other
> open issues. Marcel, can we declare this resolved, or do you want to
> keep it as a meta-issue?
the primary use of this issue was to keep track of changes in test cases
and to have an issue number for commits. I think we can close this issue
now.
regards
marcel
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/9/06, Roy T. Fielding <fi...@gbiv.com> wrote:
> In any case, we still need to graduate from Incubator first, so the
> branch may be a bit premature.
Ah, I was assuming that we should release first and graduate after
that, but looking back in the archives I notice that you did suggest
graduation between 0.9 and 1.0. It's no problem really, in fact it's
probably better if the 1.0 branch has a little time to cool down
before the release is made. I'll keep an eye out for low-risk changes
to Jackrabbit trunk that are important enough to be merged into the
1.0 branch.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Mar 8, 2006, at 2:46 PM, Jukka Zitting wrote:
> SLF4J 1.0 got released a short while ago and is already on it's way
> towards the ibiblio maven repository. Given that I'm in any case going
> to make a second release candidate due to the JCR-335 fix, I'd like to
> get also JCR-215 included in the release.
I think that is a good idea. I would like to get all of the interface
issues fixed in 1.0, unless we have some burning need to produce 1.0
real soon.
Note that we can't release a 1.0 until it passes the TCK, which in
turn requires the TCK exceptions list to be published by Day.
Actually, the TCK appeals procedures says that the Exclude List will
be published in Jackrabbit's trunk/test, but I think that is a mistake
(not to mention that the location moved to trunk/src/test, and will
move again when Jackrabbit graduates from incubator). The actual
location is near the same place that the TCK is downloaded, though
the last time I looked it was empty.
In any case, we still need to graduate from Incubator first, so the
branch may be a bit premature. I just finished a round of travel, so
now is a good time to graduate.
....Roy
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/7/06, Jukka Zitting <ju...@gmail.com> wrote:
> [JCR-215] Code depends on Log4J directly
>
> Based on previous email discussions I had hoped for SLF4J 1.0 to be
> released already now. This is however not the case, so in the interest
> of avoiding unknown delays I decided to postpone this issue even
> though I declared it critical in the release plan.
SLF4J 1.0 got released a short while ago and is already on it's way
towards the ibiblio maven repository. Given that I'm in any case going
to make a second release candidate due to the JCR-335 fix, I'd like to
get also JCR-215 included in the release.
Although in practice the JCR-215 code modifications are trivial and
require no or little changes to existing log4j configurations, the
issue still changes one of the project dependencies. I will keep the
issue postponed to 1.1 if anyone feels concerned about this.
If not, I will commit the JCR-215 changes as soon as SLF4J 1.0 hits
the ibiblio repository so people can recompile and check that SLF4J
works as expected in their environments. If no problems are reported,
I will then include the change in the second Jackrabbit 1.0 release
candidate.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Re: Jackrabbit 1.0 branched
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 3/7/06, Giota Karadimitriou <Gi...@eurodyn.com> wrote:
> I would just like to refer to http://issues.apache.org/jira/browse/JCR-50
> issue which concerns persistence data not being removed properly when
> deleting a version.
>
> Is it possible to include a fix for this in release 1.0?
Unfortunately no, unless you have a patch ready that fixes this issue. :-)
> Yesterday I tracked this issue down and voted for it. I read that it was
> to be fixed in version 1.0 but today I saw that its fix has been moved
> for version 1.1.
Yes, I posponed the issue to 1.1 as described in the Jackrabbit 1.0
release plan. There is currently no active work being done on the
JCR-50 issue and so far there hasn't been that much interest in fixing
it. You did the right thing by voting on the issue, this will help get
more attention to it before Jackrabbit 1.1 gets released.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
RE: Jackrabbit 1.0 branched
Posted by Giota Karadimitriou <Gi...@eurodyn.com>.
I would just like to refer to
http://issues.apache.org/jira/browse/JCR-50
issue which concerns persistence data not being removed properly when
deleting a version.
Is it possible to include a fix for this in release 1.0?
Yesterday I tracked this issue down and voted for it. I read that it was
to be fixed in version 1.0 but today I saw that its fix has been moved
for version 1.1.
The behaviour I observed regarding this issue is that when I remove a
version and print version history, the version appears removed but if
the session is closed or the repository is shutdown the version
'miraculously' re-appears if I print the version history again.
Regards
Giota
-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com]
Sent: Tuesday, March 07, 2006 9:57 AM
To: jackrabbit-dev@incubator.apache.org
Subject: Jackrabbit 1.0 branched
Hi,
A bit later than originally planned, I've now created the 1.0 branch
and postponed a number of remaining issues to 1.1 as described in the
Jackrabbit 1.0 release plan. Please let me know if you still want to
have some changes included in 1.0.
The branch seems to be in a pretty good shape by default and the
remaining 1.0 issue (JCR-156) doesn't suggest any explicit changes, so
I will make the first release candidate already in the evening.
Comments on the issues declared critical in the Jackrabbit 1.0 release
plan:
[JCR-156] Review test cases and cross check with 1.0 specification
This is the only remaining 1.0 issue after the postponing of other
open issues. Marcel, can we declare this resolved, or do you want to
keep it as a meta-issue?
[JCR-215] Code depends on Log4J directly
Based on previous email discussions I had hoped for SLF4J 1.0 to be
released already now. This is however not the case, so in the interest
of avoiding unknown delays I decided to postpone this issue even
though I declared it critical in the release plan.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development