On Mon, Jun 10, 2013 at 7:12 PM, Afkham Azeez <[email protected]> wrote:
> The problem is, some components get used by more than one feature, and > in the future, we may decide to combine components in different ways > to create features. That is the reason why features are outside > components. > yeah, it's not related one to one. > > Azeez > > On Mon, Jun 10, 2013 at 7:05 PM, Sagara Gunathunga <[email protected]> > wrote: > > I'm not sure I'm throwing an idea that already discussed in the past and > > found negative impacts. What about to remove top level component/feature > > directories and make related component/feature together. > > > > As an example we will have webapp-mgt module and inside that we have > > webapp-mgt components and webapp-mgt feature as sub modules ? > > > > Thanks ! > > > > > > On Mon, Jun 10, 2013 at 7:01 PM, Afkham Azeez <[email protected]> wrote: > >> > >> Another process we should introduce once we have collapsed the > >> features & components is that, we should not allow addition of new > >> components & features without a review process. First we should see > >> whether that feature/component can be part of an existing > >> component/feature. Only if the developer can justify that it has to be > >> a feature/component on its own, we should allow adding it. > +1. Also we should mandate a number of patch releases that we can do upon a major release. :) For 4.0.0 it went up to 8 patch releases, and that made things messy. > >> > >> Azeez > >> > >> On Mon, Jun 10, 2013 at 6:48 PM, Supun Malinga <[email protected]> wrote: > >> > > >> > > >> > > >> > On Mon, Jun 10, 2013 at 6:41 PM, Afkham Azeez <[email protected]> wrote: > >> >> > >> >> Reducing the number of components will automatically mean that we > >> >> reduce > >> >> the number of features too. > >> > > >> > > >> > yeah. we need to change the features's structure along with the > >> > modification > >> > to the components' structure. > >> > > >> >> > >> >> > >> >> Azeez > >> >> > >> >> > >> >> On Mon, Jun 10, 2013 at 6:20 PM, Afkham Azeez <[email protected]> > wrote: > >> >>> > >> >>> We should also look into our component list & see whether there are > >> >>> components that can be deprecated. > >> >>> > >> >>> Azeez > >> >>> > >> >>> > >> >>> On Mon, Jun 10, 2013 at 6:06 PM, Afkham Azeez <[email protected]> > wrote: > >> >>>> > >> >>>> I suggest that we remove all orbits which simply wrap 3rd party > jars > >> >>>> from our main code repo, and have a separate repo for that. All > such > >> >>>> orbit > >> >>>> bundles will immediately be graduated, and deployed into the WSO2 > >> >>>> Maven > >> >>>> repo. If there is an issue with such an orbit bundle, which is a > rare > >> >>>> occurrence, you have to increment the orbit version of that bundle. > >> >>>> > >> >>>> Next step would be to start collapsing the components. For example, > >> >>>> all > >> >>>> the 50 mediator components will be collapse into the mediator BE & > >> >>>> mediator > >> >>>> FE components. > >> >>>> > >> >>>> We also need to greatly simplify the branching. When we collapse > >> >>>> components & have a smaller number of components, branching will > >> >>>> become much > >> >>>> simpler. > >> >>>> > >> >>>> > >> >>>> > >> >>>> On Mon, Jun 10, 2013 at 5:32 PM, Sagara Gunathunga < > [email protected]> > >> >>>> wrote: > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> On Mon, Jun 10, 2013 at 3:32 PM, 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. > >> >>>>> > >> >>>>> > >> >>>>> In fact during each and every release we have to spend significant > >> >>>>> amount of time to resolve issues introduced by repo structure & > >> >>>>> build > >> >>>>> structure themselves. If we can make them simple we can have very > >> >>>>> smooths > >> >>>>> release cycles and on time releases. > >> >>>>> > >> >>>>> +1 to prioritize this as an urgent requirement. > >> >>>>> > >> >>>>> Thanks ! > >> >>>>> > >> >>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> 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/ > >> >>>>>>>> > >> >>>>>>>> email: [email protected] cell: +94 77 3320919 > >> >>>>>>>> blog: http://blog.afkham.org > >> >>>>>>>> twitter: 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 > >> >>>>>>> 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/ > >> >>>>>> > >> >>>>>> email: [email protected] cell: +94 77 3320919 > >> >>>>>> blog: http://blog.afkham.org > >> >>>>>> twitter: 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 > >> >>>>>> > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> -- > >> >>>>> Sagara Gunathunga > >> >>>>> > >> >>>>> Senior Technical Lead; WSO2, Inc.; http://wso2.com > >> >>>>> V.P Apache Web Services; http://ws.apache.org/ > >> >>>>> Linkedin; http://www.linkedin.com/in/ssagara > >> >>>>> Blog ; http://ssagara.blogspot.com > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> -- > >> >>>> Afkham Azeez > >> >>>> Director of Architecture; WSO2, Inc.; http://wso2.com > >> >>>> Member; Apache Software Foundation; http://www.apache.org/ > >> >>>> > >> >>>> email: [email protected] cell: +94 77 3320919 > >> >>>> blog: http://blog.afkham.org > >> >>>> twitter: http://twitter.com/afkham_azeez > >> >>>> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> >>>> > >> >>>> Lean . Enterprise . Middleware > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> Afkham Azeez > >> >>> Director of Architecture; WSO2, Inc.; http://wso2.com > >> >>> Member; Apache Software Foundation; http://www.apache.org/ > >> >>> > >> >>> email: [email protected] cell: +94 77 3320919 > >> >>> blog: http://blog.afkham.org > >> >>> twitter: http://twitter.com/afkham_azeez > >> >>> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> >>> > >> >>> Lean . Enterprise . Middleware > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> Afkham Azeez > >> >> Director of Architecture; WSO2, Inc.; http://wso2.com > >> >> Member; Apache Software Foundation; http://www.apache.org/ > >> >> > >> >> email: [email protected] cell: +94 77 3320919 > >> >> blog: http://blog.afkham.org > >> >> twitter: 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 > >> >> > >> > > >> > > >> > > >> > -- > >> > Supun Malinga, > >> > > >> > Senior Software Engineer, > >> > WSO2 Inc. > >> > http://wso2.com > >> > http://wso2.org > >> > email - [email protected] > >> > mobile - 071 56 91 321 > >> > >> > >> > >> -- > >> Afkham Azeez > >> Director of Architecture; WSO2, Inc.; http://wso2.com > >> Member; Apache Software Foundation; http://www.apache.org/ > >> > >> email: [email protected] cell: +94 77 3320919 > >> blog: http://blog.afkham.org > >> twitter: http://twitter.com/afkham_azeez > >> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> > >> Lean . Enterprise . Middleware > > > > > > > > > > -- > > Sagara Gunathunga > > > > Senior Technical Lead; WSO2, Inc.; http://wso2.com > > V.P Apache Web Services; http://ws.apache.org/ > > Linkedin; http://www.linkedin.com/in/ssagara > > Blog ; http://ssagara.blogspot.com > > > > > > -- > Afkham Azeez > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > > email: [email protected] cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > Lean . Enterprise . Middleware > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
