On Mon, Jul 30, 2012 at 5:25 PM, Tharindu Mathew <[email protected]> wrote:
> > > On Mon, Jul 30, 2012 at 4:56 PM, Samisa Abeysinghe <[email protected]>wrote: > >> >> >> On Mon, Jul 30, 2012 at 4:10 PM, Tharindu Mathew <[email protected]>wrote: >> >>> >>> >>> On Fri, Jul 27, 2012 at 8:28 PM, Charitha Kankanamge >>> <[email protected]>wrote: >>> >>>> On Fri, Jul 27, 2012 at 8:16 PM, Samisa Abeysinghe <[email protected]>wrote: >>>> >>>>> I did my share of testing on BAM today. The Jira will tell the story. >>>>> >>>>> Before we pass the packs on to QA, I would like the team to look at >>>>> the issues I have reported and fix them all and all those around the types >>>>> I have reported. >>>>> >>>>> I would like the QA team to focus more serious testing on the packs, >>>>> such as volume testing, reliability/consistency of data testing etc. So >>>>> please fix these basic issues before the QA team takes over. >>>>> >>>> For this kind of testing, the pack is ready. UI issues, doc issues and >>> context help issues can be fixed for a later pack. Is this a blocker for QA >>> testing? We are running out of time to recognized Production level >>> complicated issues and we can't fix these last moment. >>> >> >> >> They are not blockers for QA testing. But right now, QA is only focusing >> on API-M aspects of BAM. >> >> The release need to focus on total quality if we are to release, and the >> lack of UI quality is a major issue. >> >> Also, note that, docs are required for testing as well, as tests need to >> be based on docs, to verify integrity. >> >> Finally, if we leave these kinds of quality issues behind in the UI and >> claim the UI is not done yet right, why are we not doing the UI in one go >> right and work only on the backed components? >> On the other hand, if we have this many quality issues on the UI, is >> it realistic to release on the said deadlines? >> >> The bottom line is that, it is time to fix these, until the QA team has >> more time to test the BE - the product is NOT only about BE & it is time >> that we finalize FE. >> > I agree that we have to fix these. Quality of both Docs, UI and BE is > paramount for a release. But this is still a pack at Beta release, and > these kind of issues can be present in the beta pack, but not L1s that has > broken basic functionality. > > So, now the plan is we will fix all issues reported, and get the RC out > with 0 L1s and 0 L2s. We will hand this pack to QA asap. > > Does this plan sound good? > +1 Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
