If the changes *are* going to make it into Axiom I'll finish up my Axis2
JiBX code changes tomorrow. Everything was working prior to the Axiom
rollback, with only the unit tests still incomplete.
I apologize for creating this mess through not subscribing to the proper
email list and properly tracking the state of the project, and for
wasting everyone's time as a result of my ignorance. I find it
personally somewhat ironic that I was one of the people who voted in
favor of moving Axiom out of the Axis2 tree in the first place, but then
didn't follow up on the change myself. I'll work at being a better
Apache team member in the future.
- Dennis
Davanum Srinivas wrote:
How about a quick rev of the RC? (with this patch in - say monday
morning your time?). Or even sync up with the next RC of Axis2...
thanks,
dims
On 4/21/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Davanum Srinivas wrote:
Eran,
Could you please review the test case, the code and let us know where
there could be likely problems. Am sure we can count on dennis to help
tweak the code. Yes, this is kind of late to do this, but i think we'd
be better off with this than without it.
I'm ok with this change, IFF we can release Axiom 1.0 with this change
before Axis2 1.0.
I do not exactly know the policy of releasing RC and releasing the
proper one after that. Yes, I didn't put a code freeze but what I feel
is once you have an RC, you can not do major surgeries to the code.
Basically IMHO RC is for the people to review it during that period.
So if you all people there agrees to release Axiom 1.0, with Dennis'
changes, by the end of next week according to the release plan we all
agreed, I'm ok with that.
BTW, do others need some time to see what Dennis has proposed ?
-- Chinthaka
P.S. BTW, the subject of this email is no longer valid :).
--
Davanum Srinivas : http://wso2.com/blogs/
