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 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: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
--
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org
Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
