Hi, Considering that fact that BAM and API-M should be released together we have to delay BAM release deadline to the same day. @Tharindu, Chamara how is the status of BAM release? Is it possible to delay it too?
regards, Nirodha On Wed, May 22, 2013 at 3:28 PM, Pavithra Madurangi <[email protected]>wrote: > Hi all, > > Following is the jira status of API-M 1.4.0 > https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10990 > There are 2 L2s and few L3s > > Except Google analytics and login to API store with SAML2 web SSO , we've > tested other features. Please refer [1] for more detail. We've run load > tests with different caching settings too (results can be found in the same > doc). > > But we were not able test the server performance during a long running > test. Apart from that, there are quite number of fixes to be verified > before releasing the product. So considering these facts, can we extend the > release to Tuesday. > > [1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdGthYU5iblEzVHVidjdrX29KNTVPbWc&usp=drive_web&pli=1#gid=34 > > Regards, > /Pavithra > > > > > > -- > *Pavithra Madurangi* > Senior Software Engineer - QA. > WSO2 Inc.: http://wso2.com/ > Mobile: +94777207357 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- * * *Nirodha Gallage* Senior Software Engineer, QA. Member of the Management Committee - QA Technologies WSO2 Inc.: http://wso2.com/ Mobile: +94716429078
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
