You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by Daniel Kulp <dk...@apache.org> on 2009/04/08 21:08:45 UTC

Can we release 1.5.7 real soon?

We're planning a patch release of CXF in the upcoming weeks and would REALLY 
like to get the thread safety fixes for wss4j in there.   Thus, could we start 
a 1.5.7 release in the next couple days?

I went through the changes on trunk that aren't on the branch and I see that 
the commits related to:
[WSS-99] - Adding BouncyCastle provider using addProvider ....
[WSS-175] - Removed static class variables froms WSHandler.
[WSS-171] - Improve XML encryption processing
[WSS-174] - Removed deprecated APIs/classes on trunk.
[WSS-173] - Remove unnecessary namespace definitions
are not merged there.    The only one there that I think falls into "might be 
nice" is WSS-99.  The rest are probably too risky or really shouldn't be there 
anyway.

Colm: any comments?

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


RE: Can we release 1.5.7 real soon?

Posted by Colm O hEigeartaigh <co...@progress.com>.
Yup, sounds fine. I agree with your assessment on the jira issues. I
have to do more work on WSS-99, so I can't guarantee that it'll be
backmerged. The only two open JIRAs on 1.5.7 are:

https://issues.apache.org/jira/browse/WSS-158
https://issues.apache.org/jira/browse/WSS-136

I think we can hold off on getting BouncyCastle 1.41 into maven, but
it'd be nice to get a pom for xml-sec 1.4.2. Can you spare some time to
look at this?

I'm off for a few days over the weekend, is Tuesday good for a vote?

Colm.

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: 08 April 2009 20:09
To: wss4j-dev@ws.apache.org
Subject: Can we release 1.5.7 real soon?


We're planning a patch release of CXF in the upcoming weeks and would
REALLY 
like to get the thread safety fixes for wss4j in there.   Thus, could we
start 
a 1.5.7 release in the next couple days?

I went through the changes on trunk that aren't on the branch and I see
that 
the commits related to:
[WSS-99] - Adding BouncyCastle provider using addProvider ....
[WSS-175] - Removed static class variables froms WSHandler.
[WSS-171] - Improve XML encryption processing
[WSS-174] - Removed deprecated APIs/classes on trunk.
[WSS-173] - Remove unnecessary namespace definitions
are not merged there.    The only one there that I think falls into
"might be 
nice" is WSS-99.  The rest are probably too risky or really shouldn't be
there 
anyway.

Colm: any comments?

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org