Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <4609588B.8080507@wso2.com>
Date: Tue, 27 Mar 2007 23:16:51 +0530
From: "Asankha C. Perera" <asankha@wso2.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061206)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Too many late changes for Axis2 1.2
References: <e9115cfd0703270918q5f302840if104273a24c3601d@mail.gmail.com>
	<46094B99.5090709@wso2.com> <46094DB0.6050701@thoughtcraft.com>
In-Reply-To: <46094DB0.6050701@thoughtcraft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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