Are we not cutting too close to the release to do this now? How much time will it take to do this and stabilize?
Also, what are the implications of current branching strategy when we do this? 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. Given all this, I would rather do this for Carbon 5. 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
