Re: [Axis2]Code freeze in trunk

Hi Deepal, all:

I'm in the midst of a reasonably large code change to Axiom, which I 
would like to check in before the release if possible.  I fixed a number 
of bugs, corrected some bad tests, improved SOAP version handling, and 
altered the behavior of OMText to deal with QNames in a less arcane manner.

Is it OK to wait one more day before freezing?

--Glen

Deepal Jayasinghe wrote:
> Hi All;
> 
> As we all know we are in the process of releasing Axis2 1.2 and I
> released Axis2 1.2 RC1 on yesterday (26^th March). Depending on the
> statues I will be doing RC2 on this Friday (I think we need to do that)
> and 1.2 release will be on 6^th April. Since we have completed the
> features we need to have in 1.2 I dont think we are going to commit code
> to Axis2 trunk , of course we have to fix issue and improve the
> documents, in addition to that there won't be any commit.
> 
> I have past experience in merging branch and trunk :) so this time I
> have no idea to cut a branch in the meantime dont see real requirement
> of doing so.
> 
> I saw couple of commits in jax-ws module , since you guys are continuing
> development of jax-ws stuff it will be very helpful for you to create a
> branch and continue the development there in the branch. Then we can
> continue release related development in the trunk :).
> 
> So I would like to declare a code freeze in Axis2 trunk ....
> 
> comments ........
> 
> Thanks
> Deepal
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>