[mashup-dev] 0.2 Release Candidates

[Keith Chapman]

saminda abeyruwan wrote:
> Hi All,
>
> We have decided to release WSAS 2.1 with following main dependencies.
>
> Axis2 1.3
> Axiom 1.2.5
> Axis2-Addressing module 1.3
> XMLSchema 1.3.2
> Neethi 2.0.2
> Wooden 1.0-incubating-M7b
> WSDL4J 1.6.1
>
> All other dependencies as with WSAS 2.0 expect the situation with 
> Rampart and Sandesha2. They are still in SNAPSHOT.
>
> Thus you can safely change Mashup trunk for these version.
Already done. BTW Axis2 uses WSDL4J 1.6.2, why is WSAS using 1.6.1?

Thanks,
Keith.
>
> Thank you
>
> WSAS Team
>
> Keith Chapman wrote:
>> Tyrell Perera wrote:
>>>
>>>
>>> Keith Chapman wrote:
>>>> Channa Gunawardena wrote:
>>>>> Tyrell Perera wrote:
>>>>>>
>>>>>>
>>>>>> Keith Chapman wrote:
>>>>>>> Tyrell Perera wrote:
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Since we are well on schedule with the feature set for the 0.2 
>>>>>>>> release.
>>>>>>>> I believe we can go ahead and start cutting RCs from next week. 
>>>>>>>> I would
>>>>>>>> like to suggest Wednesday, 5th Sep as a tentative date for RC 1 
>>>>>>>> and the
>>>>>>>> following 2 Wednesdays for the next two RCs.
>>>>>>>>
>>>>>>>> Given the status of QA defects and fixes by the end of week 3, 
>>>>>>>> we can
>>>>>>>> decide whether to go ahead with 0.2 on the 26th or to cut 
>>>>>>>> another RC.
>>>>>>>>
>>>>>>>> One crtical pre-RC task is to settle on WSAS and AXIS2 
>>>>>>>> branches, since
>>>>>>>> we are using snapshots of both at the moment. I think we are 
>>>>>>>> ready to
>>>>>>>> make the choice now.
>>>>>>> Actually we've made the choice already. The reson we are 
>>>>>>> depending on the WSAS trunk is due to that. As soon as WSAS 
>>>>>>> fixes its version on the trunk we will be switching to that. 
>>>>>>> WSAS trunk currently depends on Axis2 trunk. I heard that they 
>>>>>>> will be switching its dependencies to 1.3 shortly. When they do 
>>>>>>> that we can fix our versions too. We can release 0.2 with WSAS 
>>>>>>> 2.1 for sure (At the moment all our fetures work on WSAS trunk).
>>>>>> What's the release date for WSAS 2.1? Will it happen before 5th Sep?
>>>>>>
>>>>>> The way I see it, cutting our RCs using WSAS trunk is a bit 
>>>>>> risky. This will make the delta between 2 consecutive RCs high, 
>>>>>> along with the possibility of trouble.
>>>>>>
>>>>>> IMHO and in an ideal situation, the above delta should only 
>>>>>> include the defect fixes and documentation updates. Anything else 
>>>>>> means additional and avoidable risk.
>>>>>>
>>>>>>>>
>>>>>>>> I managed to get documentation reviews scheduled for the next 2 
>>>>>>>> weeks
>>>>>>>> with Marietta as well. So we can concentrate more on the 
>>>>>>>> user-guides and
>>>>>>>> api docs during this time along with fixing defects in code :)
>>>>>>>>
>>>>>>>> If I missed anything please add to the list ...
>>>>>>> The scraper stuff is not working at the moment. 
>>>>>> Is this due to the Rhino upgrade? I thought it's stable and 
>>>>>> Channa is working on the tooling side.
>>>>> Actually, since last week's discussion with Jonathan, I've been 
>>>>> more focused on the WsRequest.js changes to support the missing 
>>>>> HTTP properties, which I'm planning to include with RC1. Once 
>>>>> that's through, and depending on what sort of workload I have on 
>>>>> the JSP's of the org site (which I think is higher priority), 
>>>>
>>>> Yes the org site is on a critical path... May be we should push 
>>>> tooling to 0.3
>>>
>>> +1
>>>
>>> If it was broken from a while back, we might have to re visit the 
>>> design. 
>> I'm working on it at the moment. Should be able to pull it off...
>>
>> Thanks,
>> Keith.
>>> Postponing to 0.3 sounds like a safe option.
>>>
>>> Tyrell
>>>
>>>>
>>>> Thanks,
>>>> Keith.
>>>>> I should be able to spend some time on the tooling. Right now 
>>>>> though, no work is being done on tooling, to be included in RC1.
>>>>>
>>>>> Channa.
>>>>>>
>>>>>> I'm looking into that
>>>>>>> issue... We have to finalize on the stub generation too. Thats 
>>>>>>> critical before we cut the first RC.
>>>>>>
>>>>>> I agree. If the scraper is badly broken, let's put it into 
>>>>>> 'damage control' mode :) I'll have a look at it, so you can 
>>>>>> concentrate on stub generation.
>>>>>>
>>>>>> Tyrell
>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Tyrell
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mashup-dev mailing list
>>>> Mashup-dev at wso2.org
>>>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>>>
>>>
>>
>>
>> _______________________________________________
>> Mashup-dev mailing list
>> Mashup-dev at wso2.org
>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>
>
>
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>