What if we move all orbits out of the main codebase? Any orbit project will
immediately be graduated & pushed to the Maven repo.

Also, what if all dependencies that we change such as Axis2, Synapse, ODE
etc. are maintained outside the mainstream repo, and those are built
separately & pushed as snapshots to the Maven repo until we do a release?
Once we do a release, we can push the final fixed version. We don't need
everybody building these.


On Fri, Jun 14, 2013 at 8:40 AM, Amila Suriarachchi <[email protected]> wrote:

>
>
>
> On Thu, Jun 13, 2013 at 9:30 AM, Shameera Rathnayaka <[email protected]>wrote:
>
>> Hi Pradeep,
>>
>> On Thu, Jun 13, 2013 at 9:37 PM, Pradeep Fernando <[email protected]>wrote:
>>
>>> - we cant have two versions, we should remove one. However little
>>> complication here.
>>>
>>> We used to point the axis2 of trunk to current branched version of axis2
>>> (say axis2-1.6wso2v1 of 4.1.0 branch) till we are done with releases in
>>> branch. Once we are done with releasing the branch we create 1.6.wso2v2 in
>>> the trunk.
>>>
>>>
>>> Now the situation is bit different. We are releasing in multiple
>>> branches. (4.1.0 and 4.2.0). I can't decide on a version number for axis2
>>> in 4.2.0 branch since 4.1.0 branch development is in progress.
>>>
>>> However, since we are following a patching model in 4.1.0 kernel, there
>>> will not be any further versions of axis2 in 4.1.0 branch. Hence lets keep
>>> the 1.6.1-wso2v10 version, and remove other.
>>>
>>
>> +1 , I did my json merge to 1.6.1-wso2v10. Actually not only axis2 ,
>> transport also has  two versions and  platform/dependencies/cassandra also
>> has two versions. So we need to clean the trunk by removing all previous
>> versions. We should have one version(latest version) of each dependencies
>> in trunk.
>>
>
> +1. Trunk should have only one version of dependencies. Another problem we
> have solved with patching model :)
>
> thanks,
> Amila.
>
>>
>> Thanks,
>> Shamera.
>>
>>>
>>> thanks,
>>> --Pradeep
>>>
>>>
>>> On Thu, Jun 13, 2013 at 8:38 PM, Prabath Siriwardena 
>>> <[email protected]>wrote:
>>>
>>>> Please see
>>>> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/dependencies/axis2/
>>>>
>>>> --
>>>> Thanks & Regards,
>>>> Prabath
>>>>
>>>> Mobile : +94 71 809 6732
>>>>
>>>> http://blog.facilelogin.com
>>>> http://RampartFAQ.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Pradeep Fernando*
>>> Member, Management Committee - Platform & Cloud Technologies
>>> Senior Software Engineer;WSO2 Inc.; http://wso2.com
>>>
>>> blog: http://pradeepfernando.blogspot.com
>>> m: +94776603662
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Software Engineer - WSO2 Inc.*
>> *email: shameera AT wso2.com <[email protected]> , shameera AT 
>> apache.org<[email protected]>
>> *
>> *phone:  +9471 922 1454*
>> *
>> *
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter     : *https://twitter.com/Shameera_R
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to