I would like to request approval for defect 192655 to be included in TPTP 4.4 i4.
1. Explain why you believe this is a stop-ship defect. How does the defect manifest itself, and how will users of TPTP / consuming products be affected if the defect is not fixed? This is a TVT defect, 4 strings were identified as not being externalized. The minimun requirement for localization is to not have untranslated strings in the UI. 2. Is there a work-around? If so, why do you believe the work-around is insufficient? No 3. Is this a regression or API breakage? Explain. No 4. Does this require new API? No. 5. Who performed the code review? Guru Nagarajan. 6. Is there a test case attached to the bugzilla record? There is a TVT test case that tests this issue. 7. What is the risk associated with this fix? Low. 8. Is this fix related to any standards that TPTP adheres to? If so, who has validated that the fix continues to adhere to the standard? No. Thanks, Alexandru Nan - Software Developer phone: 905-413-6029 e-mail: [EMAIL PROTECTED] IBM Lab, 8200 Warden Ave. Markham, Ontario, Canada L6G 1C7
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
