I am requesting approval to fix bug 154749 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=154749)
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 blocking consumer product from running update manager. There is obsolete code in the profile on server plugin which results in a dependency on theorg.eclipse.jst.server.* plugins. They are not required anymore. The fix is the remove the obsolete codes and their dependencies. The fix is smoke tested on 4.2.1 code base.
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?
It's reviewed by Hubert Leung
6) Is there a test case attached to the bugzilla record?
Profile on server test cases are covered in test bucket.
7) What is the risk associated with this fix?
Low risk.
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.
------------------------------------------------------------------------------
Eugene Chan
IBM Toronto Laboratory, Canada
_______________________________________________ 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
