Close a bug

First of all, as is well known to us, you should:

  • Precise what you have written, to the extent that the others need ask the least to continue this subject.
  • Write down the bug number in the format “bug number”, for example bug 1063 .

Then, you should indicate clearly what should be continued by your successor.

  • You document a bug in French, not yet in English.
    1. In the svn commit, specify what in the English version should be done. For example:

This log tells that “check the tiny changes and reproduce them” in the English version of the Component Reference Guide should be done.

In this case, do not close the bug.

  • You document a bug in English according to the French equivalent.
    1. If you document the bug exactly following the French version, close the bug.
    2. If you add contents more than are written in French, specify what they are and tell what is still needed in French. Do not close the bug.
  • You document a bug in English first.
    1. If the documents related to the bug have no French version, close the bug after documenting.
    2. Otherwise, specify what should be done in French and leave the bug open.

Now your work with bugtracker is done. BTW, after telling a document is TO BE DONE IN EN or FR, you can assign the bug to the due person who will do the following job. I think this will save some time for elisa to assign a sea of bugs every time. Here is the list answering basically who is for what in our doc team.

For French,

        Alexiane          - TOS, TIS, components
        Marie             - TOS, TIS, components, TAC
        Elisabeth         - Installation

For English,

       Hiyam             - TDQ, TOP, MDM
       Paul              - TOS, TIS, components
       Yudong            - TAC, TOS, TIS, components
       Elisabeth         - Installation

If you have any further question, ask me or Elisabeth.

steps_to_close_a_resolved_needs_bug.txt · Last modified: 2011/12/17 03:51 (external edit)
Recent changes RSS feed Driven by DokuWiki