Supun, I think someday we'll any have to migrate into commons-vfs trunk. So best option would be to branch from commons-vfs trunk and apply the required patches from our commons-vfs branch.
We definitely need to have some QA(which covers scenarios such as ftp, sftp, smb, large file transfer etc..) around this and make sure that we applied all the required patches in our commons-vfs branch into the newly created trunk. Rajika On Thu, Mar 31, 2011 at 2:27 PM, Supun Kamburugamuva <[email protected]> wrote: > We want to create the commons-vfs branch for Carbon 3.2.0. we already > have a branch created from commons-vfs in Carbon 3.1.0. This branch > contains some fixes and features that we have done but not in the > commons-vfs trunk. Also we want some feature that are available in the > commons-vfs trunk. > > So I'm going to create the commons-vfs branch from the Carbon 3.1.0 > and then apply the required changes in the commons -vfs trunk to it. > > Thanks, > -- > Supun Kamburugamuva > Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com > Member, Apache Software Foundation; http://www.apache.org > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
