On Mon, Mar 5, 2012 at 7:26 PM, Samisa Abeysinghe <[email protected]> wrote:
> Are we not cutting too close to the release to do this now? How much time > will it take to do this and stabilize? > Even now the kernel, platform & orbit POMs are independent. So, doing SVN moves to different locations will not have any implications. However, we should not be moving too often since it affects all other related systems. > > Also, what are the implications of current branching strategy when we do > this? > The branching strategy will have to be rethought anyway IMO since the trunk SVN structure has changed. I believe it will become simpler since the individual branches will reside inside kernel, platform & orbit. We will first do a kernel release, and that will have a branch. Based on that kernel release, we will do platform releases. We can maintain the individual platform branches inside the platform. > Also, we need a new svn server hosted for this, where we can control > access to specific locations at a given time. The current svn does not > allow that, and hence have little use of doing this on a flat permission > schema. > SVN server move can be done even later, provided that the SVN tree structure is preserved, the outside parties may not relaize any different. For example, https://svn.wso2.org/repos/wso2/carbon/kernel/<https://svn.wso2.org/repos/wso2/carbon/kernel/%5Btrunk> & https://svn.wso2.org/repos/wso2/carbon/<https://svn.wso2.org/repos/wso2/carbon/kernel/%5Btrunk>platform are under the same repository now. However, in the future, we can make these independent SVN repos, and the outside parties or systems will not get affected since the URL does not change. > > Given all this, I would rather do this for Carbon 5. > I think we should first get the build to pass, and then do these SVN moves as soon as that happens. > > > > > > > On Mon, Mar 5, 2012 at 6:57 PM, Pradeep Fernando <[email protected]> wrote: > >> I'm +1. This is the structure we decided during the first discussion. >> shall we wait till sameera confirms. He was talking about some other >> structuring mechanism few days ago. >> >> --Pradeep >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *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*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
