On Mon, Jun 10, 2013 at 3:02 AM, Afkham Azeez <[email protected]> wrote:
> Unfortunately, our code repo structure & build structure is insanely > complex. This is the reason why it is so hard to prevent build breaks. We > need to think of a much simplified structure. Too much complexity always > leads to human error. We need to simplify everything, starting from the > repo structure. > +1 to have a simplified repo structure. But a major problem I see here is that there is no proper process in development. In other words one way to handle complex structures is to using proper process. For an example, how one can develop a feature hence a new version of a product based on a released carbon kernel? Current model is to develop at the branch and later commit the code back. For me this is a duplicate issue and can lost many commits. thanks, Amila. > > Azeez > > > On Mon, Jun 10, 2013 at 3:20 PM, Sriskandarajah Suhothayan > <[email protected]>wrote: > >> >> >> >> On Mon, Jun 10, 2013 at 1:48 PM, Afkham Azeez <[email protected]> wrote: >> >>> Folks, >>> Can somebody let me know how to do this? I seem to have forgotten the >>> process, and everuthing looks very confusing. Some orbit bundles are in >>> trunk, some are in different branches... it is not easy to find where the >>> Hazelcast orbit is :( >>> >>> The Hazelcast orbit[1] was removed as its now graduated >> >> This orbit bundle will be needed by all components & the kernel. >>> >> >> If you are directly using the the lib to build the bundle then that need >> to be added to the main orbit >> The orbits under the dependencies are only used to bundle the relevant >> dependencies >> >> Suho >> >> [1] >> https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/hazelcast/2.2.wso2v1/ >> >> >> >>> >>> >>> -- >>> *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 >>> >>> >> >> >> -- >> *S. Suhothayan >> * >> Associate Technical Lead, >> Management Committee Member, Data Technologies Team, >> *WSO2 Inc. *http://wso2.com * >> <http://wso2.com/>* >> lean . enterprise . middleware >> >> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >> twitter: http://twitter.com/suhothayan | linked-in: >> http://lk.linkedin.com/in/suhothayan* >> * >> * >> > > > > -- > *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* > -- *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
