We have 14 +1 votes with (10 binding).
There is a -1 vote from Jim Ma. It relates to a J2EE TCK failure. However,
the standalone TCK's do pass so that doesn't affect CXF when used standalone.
It would only affect app servers embedding CXF.
Thus, I'm going to mark this vote as passed and
OK, at least it's clear what the situation is :-)
With my Apache hat on, here is my +1 to the 2.3.2 release, even with
this issue the release is fine.
We'll fix this in 2.3.3 ;-)
Cheers
Alessio
On 01/20/2011 02:11 PM, Jim Ma wrote:
Thanks Dan. My fix to CXF-3209 introduced these regression f
Thanks Dan. My fix to CXF-3209 introduced these regression failures
. I've reverted these changes in 2.3.x branch . I'll look this issue
again and provide some better test for it .
On Thu, Jan 20, 2011 at 1:08 PM, Daniel Kulp wrote:
>
> I want to give Jim a bit more time to investigate what is
+1
On Tue, Jan 18, 2011 at 05:26, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Camel and ServiceMix.
>
> No
+1
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: 18 January 2011 04:26
To: dev@cxf.apache.org
Subject: [VOTE] Apache CXF 2.3.2
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite
Hi Dan,
thanks for the time for Jim to investigate this a bit further.
I agree on the whole line below btw.
Cheers
Alessio
On 01/20/2011 06:08 AM, Daniel Kulp wrote:
I want to give Jim a bit more time to investigate what is causing the
failures. I chatted with him a bit on IRC and I'm not exac
I want to give Jim a bit more time to investigate what is causing the
failures. I chatted with him a bit on IRC and I'm not exactly sure how the
test is SUPPOSED to work at all so it's hard to say what is going on.
THAT said, -1's on release votes are not a veto. Thus, as release manager,
it
I don't think a new vote is necessary, because as stated the vote covers
both portions. So everyone has voted +1 and +1 up to Jim.
To be valid, a veto must have a justifiable reason, and Jim certainly
does have one for CXF 2.3.2 but not CXF XJC 2.3.2, so the latter can
still proceed (if desir
Maybe we can consider to release XJC 2.3.2 as it doesn't relate to TCK
failures. And we don't need to cut new version of XJC 2.3.2 again.
Can we start a new vote for CXF XJC 2.3.2 ?
Willem
On 1/20/11 11:02 AM, Jim Ma wrote:
I have to vote -1 for this release.
The new changes in tagged CXF 2.3.
I have to vote -1 for this release.
The new changes in tagged CXF 2.3.2 introduced several JEE6 TCK
regression failures . I am looking for a quick fix for these failures.
Jim
On Wed, Jan 19, 2011 at 8:28 AM, Eric Johnson wrote:
> +1
>
> On Tue, Jan 18, 2011 at 6:31 PM, Christian Schneider
> wr
+1
On Tue, Jan 18, 2011 at 6:31 PM, Christian Schneider
wrote:
> +1
>
> Christian
>
>
> Am 18.01.2011 05:26, schrieb Daniel Kulp:
>>
>> We've had a busy 8 weeks or so despite the holidays. We've managed to
>> fix over 75 JIRA issues since 2.3.1 which is quite remarkable . This also
>> fixes a
+1
Christian
Am 18.01.2011 05:26, schrieb Daniel Kulp:
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes a
bunch of OSGi related issues that are needed for
Camel and ServiceMix.
Note: thi
+1 (non-binding)
Hadrian
On Jan 17, 2011, at 11:26 PM, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Came
+1
Jeff
On Jan 17, 2011, at 9:26 PM, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Camel and ServiceMix.
my +1 vote
From: Daniel Kulp [dk...@apache.org]
Sent: Monday, January 17, 2011 11:26 PM
To: dev@cxf.apache.org
Subject: EXTERNAL: [VOTE] Apache CXF 2.3.2
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 J
On Monday 17 January 2011 11:58:27 pm Johan Edstrom wrote:
> Dan,
>
> Do we have a transition guide on this?
> I'm 100% for a move, where does this hit existing 2.x code?
Migration guides are at:
http://cxf.apache.org/docs/migration-guides.html
Dan
>
> On Jan 17, 2011, at 9:26 PM, Daniel Kulp
Dan,
Do we have a transition guide on this?
I'm 100% for a move, where does this hit existing 2.x code?
On Jan 17, 2011, at 9:26 PM, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable
+1,
Ulhas Bhole
On 18 Jan 2011, at 04:26, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Camel and ServiceM
+1
Thanks
Freeman
On 2011-1-18, at 下午12:26, Daniel Kulp wrote:
We've had a busy 8 weeks or so despite the holidays. We've managed
to fix over 75 JIRA issues since 2.3.1 which is quite remarkable .
This also fixes a bunch of OSGi related issues that are needed for
Camel and ServiceMix.
+1
David
On 18 January 2011 04:26, Daniel Kulp wrote:
>
> We've had a busy 8 weeks or so despite the holidays. We've managed to fix
> over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes
> a bunch of OSGi related issues that are needed for
> Camel and ServiceMix.
>
>
+1
Cheers, Sergey
> On 17.01.2011 23:26, Daniel Kulp wrote:
>
>> We've had a busy 8 weeks or so despite the holidays. We've managed to
>> fix over 75 JIRA issues since 2.3.1 which is quite remarkable . This also
>> fixes a bunch of OSGi related issues that are needed for
>> Camel and ServiceM
+1
Glen
On 17.01.2011 23:26, Daniel Kulp wrote:
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes a
bunch of OSGi related issues that are needed for
Camel and ServiceMix.
Note: this vote a
We've had a busy 8 weeks or so despite the holidays. We've managed to fix
over 75 JIRA issues since 2.3.1 which is quite remarkable . This also fixes a
bunch of OSGi related issues that are needed for
Camel and ServiceMix.
Note: this vote also includes a release of the cxf-xjc-utils to fix
23 matches
Mail list logo
