Hi,

In the attached excel file there is the list of orbits at [1]. That list
indicates the orbits needed to be graduated and the orbits needed to be
version upgraded. It's important to note that when someone is doing a
commit to an orbit, it's required to do a version upgrade of that orbit.


[1] https://svn.wso2.org/repos/wso2/trunk/carbon/orbit/

Thanks,
 - Chethiya

On Sat, Feb 11, 2012 at 7:00 PM, Dileepa Jayakody <[email protected]> wrote:

> Hi All,
>
> The dependencies are now split into carbon dependencies[1] and graphite
> dependencies[2] and related orbits are taken inside them.
>
> When considering dependencies/transports; carbon only has dependencies to
> axis2-transport-base, axis2-transport-jms and axis2-json.
> Since these artifacts are built inside transports/modules, the whole
> transports dependency project has been moved into carbon/dependencies in
> the new svn structure at the moment.
>
> There are several other modules inside transports which are not needed for
> carbon AFAIU. Can we split transports project so that only the carbon
> dependency transports modules are taken inside carbon/dependencies and the
> rest are moved to graphite/dependencies? WDYT?
>
> [1]
> https://svn.wso2.org/repos/wso2/scratch/carbon-svn-re-org/dependencies/
> [2] https://svn.wso2.org/repos/wso2/scratch/graphite/dependencies/
>
> Thanks,
> Dileepa
>
> On Sat, Feb 11, 2012 at 2:08 PM, Sameera Jayasoma <[email protected]>wrote:
>
>> Hi Devs,
>>
>> We(Chethiya, Dileepa, Pradeep and myself) are working on this at the
>> moment. As per the discussion we are doing all these changes on a scratch
>> area[1][2]. Once this is stable, we will migrate these changes the trunk.
>>
>> Task Distribution.
>>
>> 1) Cleanup the dependencies project. Identify the dependency projects
>> which should go to carbon and graphite. Make orbit projects for those
>> dependency projects if necessary (Dileepa)
>>
> 2) Cleanup the orbits project. Graduating the released orbit projects.
>> Coming up with a top level project for carbon-orbits.(Chethiya)
>> 3) Cleanup the core/service-stubs projects. (Pradeep)
>> 4) Cleanup the component/features/products (Sameera)
>>
>> Thanks,
>> Sameera.
>>
>> [1] https://svn.wso2.org/repos/wso2/scratch/carbon-svn-re-org
>> [2] https://svn.wso2.org/repos/wso2/scratch/graphite
>>
>> On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma <[email protected]>wrote:
>>
>>> *Objective*:
>>> Make Carbon core a top level project in WSO2 trunk. At the moment
>>> complete Carbon platform code lies under
>>> https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its
>>> own problems.
>>>
>>> *Motivations*:
>>> 1) Carbon core can be treated as a separate product which has its own
>>> dependencies, orbit and Carbon core can be released independently of other
>>> Carbon components, products.
>>> 2) To ensure that the Carbon based products can depend on a stable, well
>>> tested and released version of Carbon instead of the Carbon trunk.
>>> 3) This will also ensure the stability of the Carbon based products,
>>> because they are no longer depend on the Carbon trunk which might undergo
>>> drastic changes time to time.
>>>
>>> *Execution*:
>>> Here is my proposal.
>>> 1) We need to create two top level directories for Carbon and for
>>> components, features and Carbon based products. Sample structure is shown
>>> below.
>>>
>>> carbon
>>> |--dependencies
>>> |--orbits
>>> |--core (core set of bundles.)
>>> |--features (Carbon core features)
>>> |--product (Carbon product)
>>>
>>> X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva
>>> once mentioned this name. :) )
>>> |--dependencies
>>> |--orbits
>>> |--components
>>> |--features
>>> |--products
>>>
>>> 2) In order to change the existing svn structure to a structure like
>>> above, we need to hold all the commits, say for two to three days and
>>> restructure the SVN, test properly and release for commits.
>>>
>>> Please feel free to comment.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> Sameera Jayasoma
>>> Technical Lead and Product Manager, WSO2 Carbon
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: [email protected]
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: [email protected]
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> _______________________________________________
>> Architecture mailing list
>> [email protected]
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Dileepa Jayakody,
> Software Engineer, WSO2 Inc.
>
> Lean . Enterprise . Middleware
>
> Mobile : +94777-857616
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: [email protected]     phone: +94 777334874
blog: chethiya3000.blogspot.com

Attachment: orbits in carbon trunk.ods
Description: application/vnd.oasis.opendocument.spreadsheet

_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to