You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Daniel Kulp <dk...@apache.org> on 2009/03/12 19:36:46 UTC
Status of 2.2......
Just wanted to give an update on my status for getting 2.2 out. I'm still
hoping to do the 2.2 builds this weekend at some point so we're getting really
close. What's left on my "todo" list includes:
1) Get WSS4J 1.5.6 released. This is looking pretty good to be done
tomorrow.
2) Get the Security samples moved from sandbox into the samples. I'm waiting
for some more fixes from Eamonn first as I don't want to mess up his patches.
3) Quick bug triage - I'm planning to look through the recently added stuff
and see if anything is "quickly" fixable. (stuff with patches are good
candidates) Then get versions updated, etc...
4) Update release notes, check legal muck, etc...
Could everyone also look at the 2.2 migration guide:
http://cxf.apache.org/22-migration-guide.html
and add any updates that you know about, if any?
Anyone have anything else to add? Any major "blockers" that would hold this
up any longer? (I'm hoping not)
Keep in mind, I'm then hoping to do a 2.2.1 fairly quickly (4 weeks maybe?) to
correct any issues people find. Thus, if a fix isn't "blocker", it can be
done in the next couple weeks.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Status of 2.2......
Posted by Daniel Kulp <dk...@apache.org>.
Quick update....
On Thu March 12 2009 2:36:46 pm Daniel Kulp wrote:
> 1) Get WSS4J 1.5.6 released. This is looking pretty good to be done
> tomorrow.
This is done. Waiting for it to sync to central. (likewise for XmlSchema
1.4.4)
> 2) Get the Security samples moved from sandbox into the samples. I'm
> waiting for some more fixes from Eamonn first as I don't want to mess up
> his patches.
This is still in process. Everything is moved. I just need to update the
readme and double check they all still work as advertised.
> 3) Quick bug triage - I'm planning to look through the recently added stuff
> and see if anything is "quickly" fixable. (stuff with patches are good
> candidates) Then get versions updated, etc...
"good enough". Obviously, there are still a lot of open issues, but if they
don't supply patches.................... ;-)
I may have a chance tomorrow to look at some more fixes, but I might not. If
anyone else has stuff to get in, get it in asap.
> 4) Update release notes, check legal muck, etc...
Done.
> 5) Run JAX-WS TCK and hope all is well. :-)
Done.
So, basically, we're looking good to do the builds at some point this weekend.
I'm hoping for tomorrow night, but that may depend on how well my kids behave.
:-)
Dan
>
> Could everyone also look at the 2.2 migration guide:
> http://cxf.apache.org/22-migration-guide.html
> and add any updates that you know about, if any?
>
> Anyone have anything else to add? Any major "blockers" that would hold
> this up any longer? (I'm hoping not)
>
> Keep in mind, I'm then hoping to do a 2.2.1 fairly quickly (4 weeks maybe?)
> to correct any issues people find. Thus, if a fix isn't "blocker", it can
> be done in the next couple weeks.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Status of 2.2......
Posted by Sergey Beryozkin <sb...@progress.com>.
>
> Anyone have anything else to add? Any major "blockers" that would hold this
> up any longer? (I'm hoping not)
I should be ok too - will do few minor updates to the client api plus fix few other minor issues
Cheers, Sergey
>
> Keep in mind, I'm then hoping to do a 2.2.1 fairly quickly (4 weeks maybe?) to
> correct any issues people find. Thus, if a fix isn't "blocker", it can be
> done in the next couple weeks.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
Re: Status of 2.2......
Posted by Daniel Kulp <dk...@apache.org>.
Forgot one more item:
5) Run JAX-WS TCK and hope all is well. :-)
Dan
On Thu March 12 2009 2:36:46 pm Daniel Kulp wrote:
> Just wanted to give an update on my status for getting 2.2 out. I'm still
> hoping to do the 2.2 builds this weekend at some point so we're getting
> really close. What's left on my "todo" list includes:
>
> 1) Get WSS4J 1.5.6 released. This is looking pretty good to be done
> tomorrow.
>
> 2) Get the Security samples moved from sandbox into the samples. I'm
> waiting for some more fixes from Eamonn first as I don't want to mess up
> his patches.
>
> 3) Quick bug triage - I'm planning to look through the recently added stuff
> and see if anything is "quickly" fixable. (stuff with patches are good
> candidates) Then get versions updated, etc...
>
> 4) Update release notes, check legal muck, etc...
>
> Could everyone also look at the 2.2 migration guide:
> http://cxf.apache.org/22-migration-guide.html
> and add any updates that you know about, if any?
>
> Anyone have anything else to add? Any major "blockers" that would hold
> this up any longer? (I'm hoping not)
>
> Keep in mind, I'm then hoping to do a 2.2.1 fairly quickly (4 weeks maybe?)
> to correct any issues people find. Thus, if a fix isn't "blocker", it can
> be done in the next couple weeks.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
RE: Status of 2.2......
Posted by Eamonn Dwyer <EA...@progress.com>.
Hi Dan
I've just included the fixes I have as a patch to
CXF-2111
Regards
Eamonn
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: 12 March 2009 18:37
To: dev@cxf.apache.org
Subject: Status of 2.2......
Just wanted to give an update on my status for getting 2.2 out. I'm
still
hoping to do the 2.2 builds this weekend at some point so we're getting
really
close. What's left on my "todo" list includes:
1) Get WSS4J 1.5.6 released. This is looking pretty good to be done
tomorrow.
2) Get the Security samples moved from sandbox into the samples. I'm
waiting
for some more fixes from Eamonn first as I don't want to mess up his
patches.
3) Quick bug triage - I'm planning to look through the recently added
stuff
and see if anything is "quickly" fixable. (stuff with patches are good
candidates) Then get versions updated, etc...
4) Update release notes, check legal muck, etc...
Could everyone also look at the 2.2 migration guide:
http://cxf.apache.org/22-migration-guide.html
and add any updates that you know about, if any?
Anyone have anything else to add? Any major "blockers" that would hold
this
up any longer? (I'm hoping not)
Keep in mind, I'm then hoping to do a 2.2.1 fairly quickly (4 weeks
maybe?) to
correct any issues people find. Thus, if a fix isn't "blocker", it can
be
done in the next couple weeks.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog