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 Thilina Gunarathne <cs...@gmail.com> on 2007/03/27 18:18:27 UTC
[Axis2] Too many late changes for Axis2 1.2
Hi all,
I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
the momentum of changes increased a bit recently Eg: QName, naming of
stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
I'm little bit worried about our readiness for the Axis2 1.2 release.
IMHO Axis2 needs a lot of testing.. I would also like to see couple of
more RC's too.. This is the same thing which happened for the 1.0
release, with too many late major changes it lost it's stability.. We
should always keep our 1.0 experiences in mind..
Personally I prefer delaying a release by couple of days rather than
going ahead with something which I'm not soo comfortable with... I'm
know this same paranoid feeling made the Axis2 1.1 release delayed
by days or weeks :(. But I prefer it that way..
Thanks,
Thilina
--
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] Too many late changes for Axis2 1.2
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Glen
Yes, I agree that Axiom should have had unit tests that failed - instead
of Axis2. But unfortunately as Axis2 had fixed the axiom version to
1.2.3-RC1 in maven and even those failures were not apparent in any of
the build reports. So if we are to make changes in Axiom, we should
revert the Axis2 dependency for Axiom to SNAPSHOT and make sure that the
build process would test the changes through integration tests.
asankha
Glen Daniels wrote:
> Hi Asankha:
>
> There are (at least) two issues here. One is last-minute changes,
> sure (and I do agree that we should delay the release by a week or
> so). The other, MUCH MORE SERIOUS ONE, is that we aren't adequately
> testing our base libraries. If addressing got broken by a change in
> Axiom, then it was clearly relying on something in Axiom which wasn't
> being tested by Axiom. We need to be better about this - I previously
> commented on this kind of thing in [1].
>
> We have a lot of tests but we need to make sure that they are the
> RIGHT tests.
>
> --Glen
>
> [1] http://www.mail-archive.com/axis-dev@ws.apache.org/msg29566.html
>
> Asankha C. Perera wrote:
>> I agree with Thilina, Last night I found out that the latest changes
>> in Axiom breaks addressing and alerted Deepal. A minor bug in Axiom
>> could lead to many issues and Addressing just seems to be one such
>> case. As soon as a broken Axiom appears in the Maven repos it spills
>> down to all smaller projects below and breaks the builds. More
>> changes pending in Axiom at this last minute could be good or bad..
>> but it certainly scares me a bit
>>
>> asankha
>>
>> Thilina Gunarathne wrote:
>>> Hi all,
>>> I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
>>> the momentum of changes increased a bit recently Eg: QName, naming of
>>> stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
>>>
>>> I'm little bit worried about our readiness for the Axis2 1.2 release.
>>> IMHO Axis2 needs a lot of testing.. I would also like to see couple of
>>> more RC's too.. This is the same thing which happened for the 1.0
>>> release, with too many late major changes it lost it's stability.. We
>>> should always keep our 1.0 experiences in mind..
>>>
>>> Personally I prefer delaying a release by couple of days rather than
>>> going ahead with something which I'm not soo comfortable with... I'm
>>> know this same paranoid feeling made the Axis2 1.1 release delayed
>>> by days or weeks :(. But I prefer it that way..
>>>
>>> Thanks,
>>> Thilina
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Too many late changes for Axis2 1.2
Posted by Thilina Gunarathne <cs...@gmail.com>.
Just to be clear, I'm not against any of the recent changes :) ..There
were very good reasons behind them...
As for this release we need to do more external testing to cover up
our lack of unit tests..
For the long run, I certainly agree that we need more unit tests to
the Axiom, which is the heart of apache new generation WS projects...
thanks,
Thilina
On 3/27/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Asankha:
>
> There are (at least) two issues here. One is last-minute changes, sure
> (and I do agree that we should delay the release by a week or so). The
> other, MUCH MORE SERIOUS ONE, is that we aren't adequately testing our
> base libraries. If addressing got broken by a change in Axiom, then it
> was clearly relying on something in Axiom which wasn't being tested by
> Axiom. We need to be better about this - I previously commented on this
> kind of thing in [1].
>
> We have a lot of tests but we need to make sure that they are the RIGHT
> tests.
>
> --Glen
>
> [1] http://www.mail-archive.com/axis-dev@ws.apache.org/msg29566.html
>
> Asankha C. Perera wrote:
> > I agree with Thilina, Last night I found out that the latest changes in
> > Axiom breaks addressing and alerted Deepal. A minor bug in Axiom could
> > lead to many issues and Addressing just seems to be one such case. As
> > soon as a broken Axiom appears in the Maven repos it spills down to all
> > smaller projects below and breaks the builds. More changes pending in
> > Axiom at this last minute could be good or bad.. but it certainly scares
> > me a bit
> >
> > asankha
> >
> > Thilina Gunarathne wrote:
> >> Hi all,
> >> I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
> >> the momentum of changes increased a bit recently Eg: QName, naming of
> >> stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
> >>
> >> I'm little bit worried about our readiness for the Axis2 1.2 release.
> >> IMHO Axis2 needs a lot of testing.. I would also like to see couple of
> >> more RC's too.. This is the same thing which happened for the 1.0
> >> release, with too many late major changes it lost it's stability.. We
> >> should always keep our 1.0 experiences in mind..
> >>
> >> Personally I prefer delaying a release by couple of days rather than
> >> going ahead with something which I'm not soo comfortable with... I'm
> >> know this same paranoid feeling made the Axis2 1.1 release delayed
> >> by days or weeks :(. But I prefer it that way..
> >>
> >> Thanks,
> >> Thilina
> >>
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
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] Too many late changes for Axis2 1.2
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Asankha:
There are (at least) two issues here. One is last-minute changes, sure
(and I do agree that we should delay the release by a week or so). The
other, MUCH MORE SERIOUS ONE, is that we aren't adequately testing our
base libraries. If addressing got broken by a change in Axiom, then it
was clearly relying on something in Axiom which wasn't being tested by
Axiom. We need to be better about this - I previously commented on this
kind of thing in [1].
We have a lot of tests but we need to make sure that they are the RIGHT
tests.
--Glen
[1] http://www.mail-archive.com/axis-dev@ws.apache.org/msg29566.html
Asankha C. Perera wrote:
> I agree with Thilina, Last night I found out that the latest changes in
> Axiom breaks addressing and alerted Deepal. A minor bug in Axiom could
> lead to many issues and Addressing just seems to be one such case. As
> soon as a broken Axiom appears in the Maven repos it spills down to all
> smaller projects below and breaks the builds. More changes pending in
> Axiom at this last minute could be good or bad.. but it certainly scares
> me a bit
>
> asankha
>
> Thilina Gunarathne wrote:
>> Hi all,
>> I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
>> the momentum of changes increased a bit recently Eg: QName, naming of
>> stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
>>
>> I'm little bit worried about our readiness for the Axis2 1.2 release.
>> IMHO Axis2 needs a lot of testing.. I would also like to see couple of
>> more RC's too.. This is the same thing which happened for the 1.0
>> release, with too many late major changes it lost it's stability.. We
>> should always keep our 1.0 experiences in mind..
>>
>> Personally I prefer delaying a release by couple of days rather than
>> going ahead with something which I'm not soo comfortable with... I'm
>> know this same paranoid feeling made the Axis2 1.1 release delayed
>> by days or weeks :(. But I prefer it that way..
>>
>> Thanks,
>> Thilina
>>
>
> ---------------------------------------------------------------------
> 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] Too many late changes for Axis2 1.2
Posted by "Asankha C. Perera" <as...@wso2.com>.
I agree with Thilina, Last night I found out that the latest changes in
Axiom breaks addressing and alerted Deepal. A minor bug in Axiom could
lead to many issues and Addressing just seems to be one such case. As
soon as a broken Axiom appears in the Maven repos it spills down to all
smaller projects below and breaks the builds. More changes pending in
Axiom at this last minute could be good or bad.. but it certainly scares
me a bit
asankha
Thilina Gunarathne wrote:
> Hi all,
> I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
> the momentum of changes increased a bit recently Eg: QName, naming of
> stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
>
> I'm little bit worried about our readiness for the Axis2 1.2 release.
> IMHO Axis2 needs a lot of testing.. I would also like to see couple of
> more RC's too.. This is the same thing which happened for the 1.0
> release, with too many late major changes it lost it's stability.. We
> should always keep our 1.0 experiences in mind..
>
> Personally I prefer delaying a release by couple of days rather than
> going ahead with something which I'm not soo comfortable with... I'm
> know this same paranoid feeling made the Axis2 1.1 release delayed
> by days or weeks :(. But I prefer it that way..
>
> Thanks,
> Thilina
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Too many late changes for Axis2 1.2
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 from me; we need to put out another rock solid stable release like 1.1
and 1.1.1 were.
Sanjiva.
Thilina Gunarathne wrote:
> Hi all,
> I've been seen lot of changes happening in the Axis2 lately.. AFAIKS
> the momentum of changes increased a bit recently Eg: QName, naming of
> stubs, lots of AXIOM changes, WSDL2 integration, etc,etc...
>
> I'm little bit worried about our readiness for the Axis2 1.2 release.
> IMHO Axis2 needs a lot of testing.. I would also like to see couple of
> more RC's too.. This is the same thing which happened for the 1.0
> release, with too many late major changes it lost it's stability.. We
> should always keep our 1.0 experiences in mind..
>
> Personally I prefer delaying a release by couple of days rather than
> going ahead with something which I'm not soo comfortable with... I'm
> know this same paranoid feeling made the Axis2 1.1 release delayed
> by days or weeks :(. But I prefer it that way..
>
> Thanks,
> Thilina
>
--
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