Re: [VOTE] Release Apache Jackrabbit 1.2.2
Hi, well, the issue may leave the repository in an unusable state: in more detail, the root node might contain an entry in its child node entry list with no corresponding child node. Is that critical enough? Cheers Dominique On 2/19/07, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, On 2/19/07, Dominique Pfister [EMAIL PROTECTED] wrote: I was just pointed to some clustering issue, occurring with simultaneous processes that add/delete children on the same parent node. I was able to identify the source of this error and to fix it, and I would be very glad to include this fix in the upcoming 1.2.2 release. Could you defer the release for 1 or 2 days, or is it already too late? Too late, unless the issue is a critical enough to justify voting -1 in the ongoing release vote. I'm planning to release 1.3 already in March, but if there's demand to get a fix for this issue out already before that, then an earlier 1.2.3 patch release is definitely possible. BR, Jukka Zitting
[RESULT] [VOTE] Release Apache Jackrabbit 1.2.2
Hi, On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote: Please vote on releasing these packages as Apache Jackrabbit 1.2.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. The vote passes with four binding +1 votes and one non-binding +1 vote. The binding votes were: +1 Jukka Zitting +1 Stefan Guggisberg +1 Tobias Bocanegra +1 Marcel Reutegger The non-binding vote was: +1 Fabrizio Giustina Thanks for voting! I'll proceed to make the public release announcement tomorrow once the release has been replicated through the mirroring system. I'll also push the release artifacts to the Maven repositories. BR, Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 1.2.2
Hi, On 2/20/07, Dominique Pfister [EMAIL PROTECTED] wrote: well, the issue may leave the repository in an unusable state: in more detail, the root node might contain an entry in its child node entry list with no corresponding child node. Is that critical enough? As far as I understood the problem only affects a specific concurrent use case when clustering is enabled. Thus I'd label it as a major issue but not critical, especially since clustering is still marked as a beta feature for the 1.2 branch. Please file it as a bug report for this and I'll consider making a 1.2.3 release once the issue is fixed. BR, Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 1.2.2
On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote: Please vote on releasing these packages as Apache Jackrabbit 1.2.2. a non binding +1 from a user, hoping that devs will cast their positive vote soon ;) cheers fabrizio
Re: [VOTE] Release Apache Jackrabbit 1.2.2
On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote: Please vote on releasing these packages as Apache Jackrabbit 1.2.2. +1 Release the packages as Apache Jackrabbit 1.2.2 cheers stefan
Re: [VOTE] Release Apache Jackrabbit 1.2.2
+1 Release the packages as Apache Jackrabbit 1.2.2 regards, toby On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, I have posted a candidate for the Apache Jackrabbit 1.2.2 release at http://people.apache.org/~jukka/jackrabbit/1.2.2/ See the included RELEASE-NOTES.txt file for details on release contents and latest changes. The release was made from the 1.2 branch after merging all the bug fixes listed in the release notes. Note that even though this is a patch release, I've included two clustering changes that are not strictly bug fixes on the grounds that the clustering feature is still in beta level. Please vote on releasing these packages as Apache Jackrabbit 1.2.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. [ ] +1 Release the packages as Apache Jackrabbit 1.2.2 [ ] -1 Do not release the packages because... BR, Jukka Zitting -- - [EMAIL PROTECTED] --- 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: [VOTE] Release Apache Jackrabbit 1.2.2
Jukka Zitting wrote: Please vote on releasing these packages as Apache Jackrabbit 1.2.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. +1 Release the packages as Apache Jackrabbit 1.2.2 regards marcel
Re: [VOTE] Release Apache Jackrabbit 1.2.2
Hi Jukka, I was just pointed to some clustering issue, occurring with simultaneous processes that add/delete children on the same parent node. I was able to identify the source of this error and to fix it, and I would be very glad to include this fix in the upcoming 1.2.2 release. Could you defer the release for 1 or 2 days, or is it already too late? Cheers Dominique On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, I have posted a candidate for the Apache Jackrabbit 1.2.2 release at http://people.apache.org/~jukka/jackrabbit/1.2.2/ See the included RELEASE-NOTES.txt file for details on release contents and latest changes. The release was made from the 1.2 branch after merging all the bug fixes listed in the release notes. Note that even though this is a patch release, I've included two clustering changes that are not strictly bug fixes on the grounds that the clustering feature is still in beta level. Please vote on releasing these packages as Apache Jackrabbit 1.2.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. [ ] +1 Release the packages as Apache Jackrabbit 1.2.2 [ ] -1 Do not release the packages because... BR, Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 1.2.2
Hi, On 2/19/07, Dominique Pfister [EMAIL PROTECTED] wrote: I was just pointed to some clustering issue, occurring with simultaneous processes that add/delete children on the same parent node. I was able to identify the source of this error and to fix it, and I would be very glad to include this fix in the upcoming 1.2.2 release. Could you defer the release for 1 or 2 days, or is it already too late? Too late, unless the issue is a critical enough to justify voting -1 in the ongoing release vote. I'm planning to release 1.3 already in March, but if there's demand to get a fix for this issue out already before that, then an earlier 1.2.3 patch release is definitely possible. BR, Jukka Zitting
[VOTE] Release Apache Jackrabbit 1.2.2
Hi, I have posted a candidate for the Apache Jackrabbit 1.2.2 release at http://people.apache.org/~jukka/jackrabbit/1.2.2/ See the included RELEASE-NOTES.txt file for details on release contents and latest changes. The release was made from the 1.2 branch after merging all the bug fixes listed in the release notes. Note that even though this is a patch release, I've included two clustering changes that are not strictly bug fixes on the grounds that the clustering feature is still in beta level. Please vote on releasing these packages as Apache Jackrabbit 1.2.2. The vote is open for the next 72 hours, and only votes from Jackrabbit committers are binding. The vote passes if at least three +1 votes are cast. [ ] +1 Release the packages as Apache Jackrabbit 1.2.2 [ ] -1 Do not release the packages because... BR, Jukka Zitting