Maho-san: Good ideas here, but I don't think they were expressed well, maybe I can help
1. These files must be fully QAd as a new release. If you are using QA TESTTOOL, use the full test suite. 2. If you find an issue, please use the Issue Tracker (or IssueZilla if you prefer this name) to fully document the issue. Please assign to the appropriate section. Please also check for existing issues. If you find an existing issue, vote for it. Do not create a new issue for an old one. 3. If you can fix the problem yourself, please do so. If not, please let the programmers fix it. This may take some time. 4. If you do fix the problem, create a child workspace on EIS. Please let someone do QA on your work. The goal is no regressions on closed issues. Please do not introduce new problems with your fixes. Whether you use QA Testtool or TCM does not matter, what does matter is a full QA of the product for EACH milestone build. This is imperative for a high quality product. I would like to add the following: We need to QA this on every build platform in every language. L10N testing MUST be accomplished for EACH milestone build. The quicker we find and fix minor problems, the more time that programmers can spend fixing the major problems and to allow introduction of new features. Here is something that I ask of the build teams besides the inclusion of CWS fixes: Let us know when a new feature is integrated. This is the BEST time to test and find problems, not two to three months later. Maho: As the QA lead, can this be added by Hamburg? I can create an issue if needed for this. Thank you in your assistance in this matter. James McKenzie Mac OS X QA Test Corrdinator. -----Original Message----- >From: NAKATA Maho <[EMAIL PROTECTED]> >Sent: Dec 19, 2006 4:58 PM >To: [email protected], [email protected] >Subject: [qa-dev] Re: MacOSX Intel version of SRC680_m197 packages uploaded > >Hi, >I uploaded SRC680_m197 Intel packages for MacOSX at good-day. > >Please do QA, I don't care which to use, TCM or QAtesttool, >and find bugs, if you find bugs, then raising issues, >if you cannot fix by yourself, find programmers to fix bugs. >Please create cws for these bugs, do integrations, then do QA again, >to verify the fix and not break othres...Before it becomes too late. > >All the best, >-- NAKATA, Maho ([EMAIL PROTECTED]) > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
