You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2007/03/27 07:09:51 UTC
[Axis2]Code freeze in trunk
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen Daniels wrote:
> 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.
Glen, if possible, can I know some more info about what you are changing
in Axiom? Just curious :)
Thanks,
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEe5FjON2uBzUhh8RAhgWAKCER5dqgt3qJQEzTyHGV02MyxZwnQCgii2R
jamqaxYCgEK9c+UaFEyDSJ8=
=uVm+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Davanum Srinivas <da...@gmail.com>.
Glen,
+1. IMHO, Deepal can cut a branch when he is ready. Or he can make a
branch from the tag before your checkin. I'd prefer the changes to go
in ASAP. So we can shake things out in the next day or so.
thanks,
dims
On 3/27/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> 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: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen Daniels wrote:
> 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.
Glen, if possible, can I know some more info about what you are changing
in Axiom? Just curious :)
Thanks,
Chinthaka
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEe5FjON2uBzUhh8RAhgWAKCER5dqgt3qJQEzTyHGV02MyxZwnQCgii2R
jamqaxYCgEK9c+UaFEyDSJ8=
=uVm+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Davanum Srinivas <da...@gmail.com>.
Glen,
+1. IMHO, Deepal can cut a branch when he is ready. Or he can make a
branch from the tag before your checkin. I'd prefer the changes to go
in ASAP. So we can shake things out in the next day or so.
thanks,
dims
On 3/27/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> 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: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Glen Daniels <gl...@thoughtcraft.com>.
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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Deepal Jayasinghe <de...@opensource.lk>.
He Keith;
If you have not break the build , then go ahead and commit the code.
Thanks
Deepal
keith chapman wrote:
> Hi deepal,
>
> I have updated the code to use the new MEP URI's and deprecated the
> old ones. I think it sould go into the release. I couldnt commit the
> code on sunday as there was a build failure. The code is ready now.
> Shall I commit it to the trunk?
>
> Thanks,
> Keith.
>
> On 3/27/07, *Deepal Jayasinghe* <deepal@opensource.lk
> <ma...@opensource.lk>> 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: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by keith chapman <ke...@gmail.com>.
Hi deepal,
I have updated the code to use the new MEP URI's and deprecated the old
ones. I think it sould go into the release. I couldnt commit the code on
sunday as there was a build failure. The code is ready now. Shall I commit
it to the trunk?
Thanks,
Keith.
On 3/27/07, Deepal Jayasinghe <de...@opensource.lk> 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
Re: [Axis2]Code freeze in trunk
Posted by Glen Daniels <gl...@thoughtcraft.com>.
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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Dims;
I will create a branch today (now ) :) , by looking at the commit
messages I too think its a good idea to cut a branch. In the meantime I
have no idea to post pond the release so the diff will be minimum.
Thanks
Deepal
Davanum Srinivas wrote:
> Deepal,
>
> I don't agree with this approach. If you want to make a release, then
> cut a branch for the release. trunk should always be open for
> business.
>
> thanks,
> dims
>
> On 3/27/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>
>> I agree .. IMO it'll be better to create a branch. And if we do release
>> 1.2 within a week as planned the diff will be minor. Last time we spent
>> *months* in a branch, which of course lead to major differences.
>>
>> Sanjiva.
>>
>> Thilina Gunarathne wrote:
>> >> 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.
>> > But you might have noticed the advantage of having the branch when we
>> > are going for the 1.1.1...
>> >
>> >> 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 :).
>> > Same problem... Different interface ;-)
>> >
>> > ~Thilina
>> >>
>> >> So I would like to declare a code freeze in Axis2 trunk ....
>> >>
>> >> comments ........
>> >>
>> >> Thanks
>> >> Deepal
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
>> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> Director; Open Source Initiative; http://www.opensource.org/
>> Member; Apache Software Foundation; http://www.apache.org/
>> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
> After some thought, I'm +1 to dims' position. Per-release branches are
> much easier to maintain into the future, too - you branch, release, and
> then you always have an easy place to go back and fix release-specific
> problems.
Absolute +1 to this moving forward as a release approach. This will allow
service releases in the future along with major development.
-Nick
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
Glen Daniels <gl...@thoughtcraft.com>
03/27/2007 08:48 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2]Code freeze in trunk
After some thought, I'm +1 to dims' position. Per-release branches are
much easier to maintain into the future, too - you branch, release, and
then you always have an easy place to go back and fix release-specific
problems.
Let's keep the trunk moving forward and release by branching. Release
manager is responsible for the branch, but the individual change authors
who write things that they want included in the release are the ones who
have to do the merging, RM just coordinates and acts as gatekeeper.
--Glen
Davanum Srinivas wrote:
> Deepal,
>
> I don't agree with this approach. If you want to make a release, then
> cut a branch for the release. trunk should always be open for
> business.
>
> thanks,
> dims
>
> On 3/27/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>> I agree .. IMO it'll be better to create a branch. And if we do release
>> 1.2 within a week as planned the diff will be minor. Last time we spent
>> *months* in a branch, which of course lead to major differences.
>>
>> Sanjiva.
>>
>> Thilina Gunarathne wrote:
>> >> 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.
>> > But you might have noticed the advantage of having the branch when we
>> > are going for the 1.1.1...
>> >
>> >> 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 :).
>> > Same problem... Different interface ;-)
>> >
>> > ~Thilina
>> >>
>> >> So I would like to declare a code freeze in Axis2 trunk ....
>> >>
>> >> comments ........
>> >>
>> >> Thanks
>> >> Deepal
>> >>
>> >>
>> >>
>> >>
---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder & Director; Lanka Software Foundation;
http://www.opensource.lk/
>> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> Director; Open Source Initiative; http://www.opensource.org/
>> Member; Apache Software Foundation; http://www.apache.org/
>> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Glen Daniels <gl...@thoughtcraft.com>.
After some thought, I'm +1 to dims' position. Per-release branches are
much easier to maintain into the future, too - you branch, release, and
then you always have an easy place to go back and fix release-specific
problems.
Let's keep the trunk moving forward and release by branching. Release
manager is responsible for the branch, but the individual change authors
who write things that they want included in the release are the ones who
have to do the merging, RM just coordinates and acts as gatekeeper.
--Glen
Davanum Srinivas wrote:
> Deepal,
>
> I don't agree with this approach. If you want to make a release, then
> cut a branch for the release. trunk should always be open for
> business.
>
> thanks,
> dims
>
> On 3/27/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
>> I agree .. IMO it'll be better to create a branch. And if we do release
>> 1.2 within a week as planned the diff will be minor. Last time we spent
>> *months* in a branch, which of course lead to major differences.
>>
>> Sanjiva.
>>
>> Thilina Gunarathne wrote:
>> >> 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.
>> > But you might have noticed the advantage of having the branch when we
>> > are going for the 1.1.1...
>> >
>> >> 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 :).
>> > Same problem... Different interface ;-)
>> >
>> > ~Thilina
>> >>
>> >> So I would like to declare a code freeze in Axis2 trunk ....
>> >>
>> >> comments ........
>> >>
>> >> Thanks
>> >> Deepal
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
>> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> Director; Open Source Initiative; http://www.opensource.org/
>> Member; Apache Software Foundation; http://www.apache.org/
>> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Davanum Srinivas <da...@gmail.com>.
Deepal,
I don't agree with this approach. If you want to make a release, then
cut a branch for the release. trunk should always be open for
business.
thanks,
dims
On 3/27/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> I agree .. IMO it'll be better to create a branch. And if we do release
> 1.2 within a week as planned the diff will be minor. Last time we spent
> *months* in a branch, which of course lead to major differences.
>
> Sanjiva.
>
> Thilina Gunarathne wrote:
> >> 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.
> > But you might have noticed the advantage of having the branch when we
> > are going for the 1.1.1...
> >
> >> 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 :).
> > Same problem... Different interface ;-)
> >
> > ~Thilina
> >>
> >> So I would like to declare a code freeze in Axis2 trunk ....
> >>
> >> comments ........
> >>
> >> Thanks
> >> Deepal
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I agree .. IMO it'll be better to create a branch. And if we do release
1.2 within a week as planned the diff will be minor. Last time we spent
*months* in a branch, which of course lead to major differences.
Sanjiva.
Thilina Gunarathne wrote:
>> 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.
> But you might have noticed the advantage of having the branch when we
> are going for the 1.1.1...
>
>> 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 :).
> Same problem... Different interface ;-)
>
> ~Thilina
>>
>> So I would like to declare a code freeze in Axis2 trunk ....
>>
>> comments ........
>>
>> Thanks
>> Deepal
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Davanum Srinivas <da...@gmail.com>.
Fine! if you want someone to take the responsibility for merging. I
will take it up. Provided the release happens on time :) If it does
not then all of us have to pitch in.
thanks,
dims
On 3/27/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> > But you might have noticed the advantage of having the branch when we
> > are going for the 1.1.1...
>
> I totally agree with you , but once we have a branch we are getting
> additional luxury of post ponding the release as we want, but once we
> are in the trunk we can not do so, we need to do the release the day we
> promise :)
>
> >
> >> 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 :).
> >
> > Same problem... Different interface ;-)
>
> yes , but the difference is I do not need to spend the time on merging
> the two , then it become someone else responsibility (simple as that :) )
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Deepal Jayasinghe <de...@opensource.lk>.
> But you might have noticed the advantage of having the branch when we
> are going for the 1.1.1...
I totally agree with you , but once we have a branch we are getting
additional luxury of post ponding the release as we want, but once we
are in the trunk we can not do so, we need to do the release the day we
promise :)
>
>> 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 :).
>
> Same problem... Different interface ;-)
yes , but the difference is I do not need to spend the time on merging
the two , then it become someone else responsibility (simple as that :) )
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Thilina Gunarathne <cs...@gmail.com>.
> But you might have noticed the advantage of having the branch when we
> are going for the 1.1.1...
s/are/were
>
> > 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 :).
> Same problem... Different interface ;-)
>
> ~Thilina
> >
> > So I would like to declare a code freeze in Axis2 trunk ....
> >
> > comments ........
> >
> > Thanks
> > Deepal
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
>
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]Code freeze in trunk
Posted by Thilina Gunarathne <cs...@gmail.com>.
> 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.
But you might have noticed the advantage of having the branch when we
are going for the 1.1.1...
> 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 :).
Same problem... Different interface ;-)
~Thilina
>
> So I would like to declare a code freeze in Axis2 trunk ....
>
> comments ........
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org