Guidelines for filing Internationalization and Localization bugs

Revision as of 23:32, 28 February 2008 by Pmclough (talk | contribs) (New page: '''Zimbra i18n and l10n Bug Filing Guidelines''' Guidelines for filing, updating and verifying i18n and l10n bugs for the '''ZIMBRA COLLABORATION SUITE''' Queries to Zimbra i18n and l1...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Zimbra i18n and l10n Bug Filing Guidelines

Guidelines for filing, updating and verifying i18n and l10n bugs for the ZIMBRA COLLABORATION SUITE

Queries to Zimbra i18n and l10n bugs: A) Existing bugs: [1] B) Fixed bugs: C) Both fixed and open bugs:

1. Before filing a bug, please check if the issue has already been filed HERE (n) 

- Sometimes we create duplicate bug reports but we should at least try to avoid that. - This requires everyone to look over the existing bug list. Note: It is possible that the issue has already been filed or even fixed (but not in build yet). Please be creative searching this list and help avoid double filing. - issues other than i18n and l10n can be searched HERE by selecting the respective or all components. 2. When filing or updating ZIMBRA bugs, please: A) choose proper component (Internationalization i18n or Localization l10n) - l10n issues: concerning any number of languages - i18n issues: concerning all languages and not attributable to any one language in particular. B) specify environment (OS version; browser version) 3. Write a clear summary and bug description (we'd like to clearly understand what the bug is about) - add individual languages to bug summary, i.e. [PL/BR/FR] if the issue is visible to some but not all languages. - if a bug is already assigned, it might be better to file a separate one (that can be assigned to someone else). In this case mention the original bug so it is obvious that a separate bug has been filed intentionally and is not supposed to be marked duplicate. - add [INTL] to bug summary if issue affects all languages. (no need to keep adding comments and/or screen shots concerning individual languages once a bug has [INTL] status in summary). 4. Do not add comments to bugs unless they belong there. - If you cannot find the issue in the EXISTING NEW, OPEN or FIXED BUGS LIST (), file a new bug following the guidelines

Jump to: navigation, search