Difference between revisions of "Guidelines for filing Internationalization and Localization bugs"

Line 26: Line 26:
  
  
2. When filing or updating ZIMBRA bugs, please:  
+
'''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.
  
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)
 
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.
+
'''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/pt_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.
 
- 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.
 
- 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).
 
(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
+
'''4. Do not add comments to bugs unless they belong there.'''
 +
 
 +
- If you cannot find the issue in the [http://bugzilla.zimbra.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ZCS&product=ZCS-Network&component=Internationalization+%28I18N%29&component=Localization+%28L10N%29&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&testcase_type=anywords&testcase=&support_type=anywords&support=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&resolution=FIXED&resolution=---&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&query_based_on=zimbra+i18n+l10n&field0-0-0=noop&type0-0-0=noop&value0-0-0= EXISTING NEW, OPEN or FIXED BUGS LIST], then please file a new bug following the guidelines

Revision as of 00:36, 29 February 2008

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

B) Fixed bugs

C) Both fixed and open bugs


Filing bugs

1. Before filing a bug, please check if the issue has already been filed here

- 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/pt_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, then please file a new bug following the guidelines

Jump to: navigation, search