On Sat, Dec 5, 2009 at 8:02 AM, Milinda Pathirage <[email protected]> wrote:

> I am still testing the build. We'll be able to build QA packs tomorrow
> onwards.


Good!

I am looking to get someone other than Lahiru to take care of building this
time around. If there are any volunteers, reveal yourselves :)

Samisa...


> Thanks
> Milinda
>
>
> On Fri, Dec 4, 2009 at 11:14 PM, Samisa Abeysinghe <[email protected]>wrote:
>
>> Are we done with branching for 2.0.3? Can we start building QA packs from
>> that?
>>
>> Samisa...
>>
>>
>> On Fri, Dec 4, 2009 at 11:05 PM, Milinda Pathirage <[email protected]>wrote:
>>
>>> I  moved 2.0.2.1 code to 2.0.3 directory. Now we don't have any 2.0.2.1
>>> in 2.0.3 branch. When you are fixing stuff in 2.0.2.1 please commit them to
>>> 2.0.3 also.
>>>
>>> Thanks
>>> Milinda
>>>
>>>
>>> On Fri, Dec 4, 2009 at 10:24 PM, Senaka Fernando <[email protected]>wrote:
>>>
>>>>
>>>>
>>>> On Fri, Dec 4, 2009 at 10:19 PM, Milinda Pathirage <[email protected]>wrote:
>>>>
>>>>> Hi Senaka,
>>>>>
>>>>> 2.0.2.1 is inside 2.0.2 branch. When I created new branch from 2.0.2
>>>>> they were there. What I need to know is how we handle this in new branch.
>>>>> The best option is to copy 2.0.2.1 code into 2.0.3, but I am not sure
>>>>> whether those 2.0.2.1 components are complete or not. If they are not
>>>>> complete yet we need to commit to both 2.0.3 and 2.0.2.1 when we are doing
>>>>> fixes.
>>>>>
>>>>
>>>> Well yes. :)... I guess that its a part of the process, isn't it?
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>>>
>>>>> Thanks
>>>>> Milinda
>>>>>
>>>>>
>>>>> On Fri, Dec 4, 2009 at 9:35 PM, Senaka Fernando <[email protected]>wrote:
>>>>>
>>>>>> Hi Milinda,
>>>>>>
>>>>>> On Fri, Dec 4, 2009 at 9:26 PM, Milinda Pathirage 
>>>>>> <[email protected]>wrote:
>>>>>>
>>>>>>> Hi devs,
>>>>>>>
>>>>>>> We are done with most part of the migration to new svn structure. But
>>>>>>> we have some carbon components with 2.0.2.1 version. Is it ok to change
>>>>>>> their versions to 2.0.3. Are you done with the 2.0.2.1 version of
>>>>>>> components? Do 2.0.2 has completed code for 2.0.2.1 version of those
>>>>>>> components?
>>>>>>>
>>>>>>
>>>>>> What's 2.0.2.1 components doing on the 2.0.3 branch? I guess this is a
>>>>>> new branch right? 2.0.2.x should be on the 2.0.2 or a 2.0.2.x branch 
>>>>>> isn't
>>>>>> it?
>>>>>>
>>>>>> Thanks,
>>>>>> Senaka.
>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Milinda
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Dec 3, 2009 at 6:05 AM, Tyrell Perera <[email protected]>wrote:
>>>>>>>
>>>>>>>> *Mashup Server*
>>>>>>>> Latest Product Branch:
>>>>>>>> https://svn.wso2.org/repos/wso2/branches/mashup/java/2.0.1/product
>>>>>>>> Next Patch Release Version: 2.0.2
>>>>>>>>
>>>>>>>> I will add Gadget Server once 1.0.0 is done.
>>>>>>>>
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> Tyrell
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Dec 2, 2009 at 11:27 PM, Milinda Pathirage <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi Product Teams,
>>>>>>>>>
>>>>>>>>> I have created 2.0.3 branch here[1]. Still there are work to be
>>>>>>>>> done to migrate it to new svn structure. In new svn structure 
>>>>>>>>> products also
>>>>>>>>> goes inside the branch[2]. Can you guys reply to this mail with the 
>>>>>>>>> latest
>>>>>>>>> product branch locations to be included in to this new location. Also 
>>>>>>>>> send
>>>>>>>>> the new version number for the next patch release.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Milinda
>>>>>>>>>
>>>>>>>>> [1] https://svn.wso2.org/repos/wso2/branches/carbon/2.0.3
>>>>>>>>> [2]
>>>>>>>>> https://svn.wso2.org/repos/wso2/branches/carbon/2.0.3/products/
>>>>>>>>>
>>>>>>>>> On Wed, Dec 2, 2009 at 5:11 PM, Samisa Abeysinghe <[email protected]
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> We need to start working on the next patch release, now that 2.0.3
>>>>>>>>>> is done.
>>>>>>>>>>
>>>>>>>>>> We will solely concentrate on bug fixes for 2.0.3. In the mean
>>>>>>>>>> time, 3.0.0 work will continue on the trunk.
>>>>>>>>>>
>>>>>>>>>> Minlinda is working on creating the branch. Once the branch is
>>>>>>>>>> cut, please commit all your fixes in there, in addition to the trunk.
>>>>>>>>>>
>>>>>>>>>> We will start building test packs as soon as end of this week.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Samisa...
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Samisa Abeysinghe
>>>>>>>>>> Director, Engineering - WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> http://www.wso2.com/ - "The Open Source SOA Company"
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>> [email protected]
>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Milinda Pathirage
>>>>>>>>> Product Manager, Business Process Server - WSO2 Inc
>>>>>>>>> Blog: http://blog.mpathirage.com
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Carbon-dev mailing list
>>>>>>>>> [email protected]
>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Tyrell Perera
>>>>>>>>
>>>>>>>> WSO2, Inc.; http://www.wso2.com/
>>>>>>>> "The Open Source SOA Company"
>>>>>>>>
>>>>>>>> http://www.linkedin.com/in/tyrell
>>>>>>>> http://tyrellperera.blogspot.com
>>>>>>>> http://twitter.com/tyrellperera
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Carbon-dev mailing list
>>>>>>>> [email protected]
>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Milinda Pathirage
>>>>>>> Product Manager, Business Process Server - WSO2 Inc
>>>>>>> Blog: http://blog.mpathirage.com
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Carbon-dev mailing list
>>>>>>> [email protected]
>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Senaka Fernando
>>>>>> Software Engineer
>>>>>> WSO2 Inc.
>>>>>> E-mail: [email protected];  Mobile: +94 77 322 1818
>>>>>>
>>>>>>
>>>>>> http://www.wso2.com/ - "The Open Source SOA Company"
>>>>>>
>>>>>> _______________________________________________
>>>>>> Carbon-dev mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Milinda Pathirage
>>>>> Product Manager, Business Process Server - WSO2 Inc
>>>>> Blog: http://blog.mpathirage.com
>>>>>
>>>>> _______________________________________________
>>>>> Carbon-dev mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Senaka Fernando
>>>> Software Engineer
>>>> WSO2 Inc.
>>>> E-mail: [email protected];  Mobile: +94 77 322 1818
>>>>
>>>> http://www.wso2.com/ - "The Open Source SOA Company"
>>>>
>>>> _______________________________________________
>>>> Carbon-dev mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Milinda Pathirage
>>> Product Manager, Business Process Server - WSO2 Inc
>>> Blog: http://blog.mpathirage.com
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Samisa Abeysinghe
>> Director, Engineering - WSO2 Inc.
>>
>> http://www.wso2.com/ - "The Open Source SOA Company"
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Milinda Pathirage
> Product Manager, Business Process Server - WSO2 Inc
> Blog: http://blog.mpathirage.com
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to