Hi Eranda, We re-wrote the test framework and gave it a major version number. So we had to choose 4.3.0, we need to maintain older test framework version until all tests are migrated to new test framework. We choose initial version of the test framework after discussing with Kernel team and aligned it to kernel version. However it was bit late to realize the drawbacks of that approach. BTW, I don't think there is any restriction to choose version number even in 4.2.0 branch, test framework is not a component, if you treat it in perspective of product, then this confusion should go away.
The next version of the framework should be 4.3.1. Since no body started test migration, we can remove TAF 4.3.0 from 4.2.0 branch and go ahead with the same version number in git repository. Thanks, Krishantha. On Mon, Mar 3, 2014 at 9:19 AM, Eranda Sooriyabandara <[email protected]>wrote: > Hi Krishantha, > There is a 4.3.0 version in test-automation-framework. Is there any reason > for having 4.3.x in 4.2.0 code base? If so what will be your next release > version? > > thanks > Eranda > > -- > > *Eranda Sooriyabandara*Senior Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > E-mail: eranda AT wso2.com > Mobile: +94 716 472 816 > Linked-In: http://www.linkedin.com/in/erandasooriyabandara > Blog: http://emsooriyabandara.blogspot.com/ > > > > > -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
