We should try and avoid all commits to branches given the history of problems.
So while in development, it has to go to trunk or scratch. It is at the point of release that branching should be done. Samisa... On Sunday, January 16, 2011, Afkham Azeez <az...@wso2.com> wrote: > > > On Sun, Jan 16, 2011 at 10:29 PM, Sanjiva Weerawarana <sanj...@wso2.com> > wrote: > > > What if we decide to release the first version of Foo as 0.9.0? > We can version it as whatever we want to. It is not a problem in this model. > > > Is there a way to have code in a branch but not have the component itself be > versioned? Basically a trunk within the branch for that component :). > > > Sanjiva. > > On Sun, Jan 16, 2011 at 10:21 PM, Afkham Azeez <az...@wso2.com> wrote: > > > 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 <sanj...@wso2.com> > 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 <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.Thanks > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com 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 > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com 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 > _______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
