We may have to decide on a case by case basis. In some cases, it could be the latest version, and in other cases it may be the most relevant version. The most common case will be going with the latest Carbon core version.
Azeez On Sun, Jan 16, 2011 at 8:28 PM, Senaka Fernando <sen...@wso2.com> wrote: > > > On Sun, Jan 16, 2011 at 8:09 PM, Afkham Azeez <az...@wso2.com> 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. >> > > +1. But, a question on what's latest. > > For some components, you might need to use other existing components (ex:- > BAM stuff). Now, taking BAM as an example, what would be the latest, 3.0.1? > or 3.1.0? The reason is that, BAM has not been up-to-date with the 3.1.0 > release, nor the trunk (on which 3.2.0 will be based), IIRC (at least in > December 2010). So, should 'latest' be the latest release applicable to your > component or the last release of the core platform? > > Thanks, > Senaka. > >> >> 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: **az...@wso2.com* <az...@wso2.com>* 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 >> Carbon-dev@wso2.org >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2, Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > 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: **az...@wso2.com* <az...@wso2.com>* 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 Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
