Code in the branch is live. At least some of it. This is where we will develop new version of existing components. So I don't see anything wrong with, the 1.0 version of a new component being there.
Azeez On Sun, Jan 16, 2011 at 10:17 PM, Sanjiva Weerawarana <[email protected]>wrote: > +1 but it feels weird to me to commit the code to the branch while its > being worked on. Foo is not yet released so it should be in trunk and > ideally that component should indicate the Carbon version dependency as > 3.1.0 and that's it. When its released for 3.1.0 we need to branch it with a > version number and so on but trunk should always be there it seems to me. > > Sanjiva. > > On Sun, Jan 16, 2011 at 8:09 PM, Afkham Azeez <[email protected]> wrote: > >> During a discussion over dinner with Paul & others at the offsite planning >> meeting, we came up with a strategy for developing new Carbon components. >> New components should always be developed against a released Carbon core >> version, unless that is not possible. We need to treat Carbon, Axis2 etc. >> just like any other 3rd party jars such as log4j which we use. >> >> Let's look at an example. Say, you are developing a new component called >> Foo. The latest Carbon release in 3.1.0. So, your component code will go >> under, >> >> >> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/components/foo/org.wso2.carbon.foo/1.0.0 >> >> https://svn.wso2.org/repos/wso2/branches/carbon/3.1.0/components/foo/org.wso2.carbon.foo.ui/1.0.0 >> >> Once you are done with the development of that component, you can >> separately release it, and update the P2 repo of Carbon 3.1.0. Once the >> release is done, you will have to port this code into the trunk. >> >> Thoughts welcome. >> >> Thanks >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; 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* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | > +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Afkham Azeez* Senior Software Architect & Senior Manager; 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*
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
