[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[hyades-dev] Re: PII: new strings appearing in plugin.properties
|
Correct, the PII freeze date has passed, so no new strings should have been checked-in after May 7. If it is feasible, the changes should be backed out, and you should either not use a string or re-use an old one. Do not hard-code a string in the source. If you believe that any of the new strings are critical, an emergency exception is possible, but only with approval during the next Hyades Committers call. Please let me know if any of the three strings are considered critical... otherwise, back it out. Thanks to Curtis for catching this.
I agree with Curtis' response to the IWAT message IDs question. Adding IWAT message IDs to existing messages is encouraged.
Best regards,
Rob Sinclair
Project Manager - ASQ Autonomic Computing / Hyades
IBM Software Group - Rational Software
20 Maguire Road, Lexington, MA, USA 02421
Office: 1.781.372.7839 (T/L: 403.7839)
Curtis D'Entremont/Toronto/IBM@IBMCA
Curtis D'Entremont/Toronto/IBM@IBMCA
05/12/2004 15:46
|
|
I think backing out of the changes in the source files will indeed fix the problem (if you can do that). As for the IWAT messages, I don't think this is as major, because we can still add them to each message for each language as we get the translated plugin.properties files back from the translation center. It would just be a matter of making sure this happens. Worst case is users won't see IWAT codes in the translations.
Thanks,
Curtis d'Entremont
Problem Determination Tools
IBM Toronto Lab
Phone: (905) 413-5754
E-Mail: curtispd@xxxxxxxxxx
![Inactive hide details for Allan K Pratt/Cupertino/IBM@IBMUS]()
Allan K Pratt/Cupertino/IBM@IBMUS
Allan K Pratt/Cupertino/IBM@IBMUS
05/12/2004 03:38 PM
|
|
Sounds like a date communication problem, yes. I did the Probekit change. I hadn't known that those files were locked down, and I guess others didn't know either.
Let's talk amelioration: what should we (the people who checked in late changes) do about this? Should we back out the plugin.properties file change, and the source change that uses the new strings? Then we can make our source changes in a different way: don't use a string, re-use an old string, or hard-code a string in the source that won't be translated. (I think the last one is permissible for strings that only go into error logs, right?)
What about changes that only add IWAT codes to existing strings? Are those changes allowed?
-- Allan Pratt, apratt@xxxxxxxxxx
Rational software division of IBM
![Inactive hide details for Curtis D'Entremont/Toronto/IBM@IBMCA]()
Curtis D'Entremont/Toronto/IBM@IBMCA
Curtis D'Entremont/Toronto/IBM@IBMCA
05/12/2004 12:28 PM
|
|
Hi,
I've observed some changes going into plugin.properties files after the PII drop on 5/7. These were not just IWAT codes, but new strings that were not there before. Specifically in:
org.eclipse.hyades.perfmon (5/11)
org.eclipse.hyades.probekit (5/11)
org.eclipse.hyades.uml2sd.ui (5/12)
I'm not sure why this happened.. perhaps the date was miscommunicated. As I understand it, these new strings will not get translated. Is there anything we can do about this problem?
Thanks,
Curtis d'Entremont
Problem Determination Tools
IBM Toronto Lab
Phone: (905) 413-5754
E-Mail: curtispd@xxxxxxxxxx


