Changes between Version 1 and Version 2 of HowToSubmitTicket


Ignore:
Timestamp:
May 24, 2008, 2:28:05 PM (12 years ago)
Author:
wojdyr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowToSubmitTicket

    v1 v2  
    22
    33=== historical note ===
    4 In old SourceForge tracker we had ''Bugs'', ''Patches'' and ''Feature Requests''.
     4In the old SourceForge tracker we had ''Bugs'', ''Patches'' and ''Feature Requests''.
    55Now we have ''tickets''. If you have ever used wx SF tracker, please read [wiki:WikiStart] to learn how to use the same username.
    66
    77=== introduction ===
    88Before creating a new ticket, you must login.
    9 Obviously, you should search if the bug is already submitted. If you are not sure that you encountered the same bug, open a new ticket and add a link to similar problem (`#1234` is automatically linked) in description. If you want to express interest in a bug that is already submitted, CC yourself or add more details. Or even better, try to fix it.
     9
     10Obviously, you should fist search if the bug is already submitted (use [/search?ticket=on search] for global search or queries to list tickets with the classname in [query:status!=closed&summary~=grid title] or [query:status!=closed&keywords~=wxGrid keyword]). If you are not sure that you encountered the same bug, open a new ticket and add mutual links to both tickets (`#1234` is automatically linked).
     11
     12If you want to express interest in a bug that is already submitted, CC yourself or add more details. Or even better, try to fix it.
    1013
    1114=== summary ===
     
    2629
    2730=== keywords ===
    28 Use full C++ names of relevant classes as keywords (e.g. `wxFileDialog`, not `file dialog` or `FileDialog`).
     31Use full C++ names of relevant classes as keywords (e.g. `wxFileDialog`, not ~~`file dialog`~~ nor ~~`FileDialog`~~).
    2932
    3033If your platform is not very popular, add it also as a keyword (e.g. Solaris, IRIX, Win9x).
    3134
    32 Other suggested keywords are: `printing`, `dnd` (for drag'n'drop problems), `transparency` (for alpha-channel problems).
     35Other suggested keywords are:
     36  * `printing`,
     37  * `dnd` (for drag'n'drop problems),
     38  * `transparency` (for alpha-channel problems).
    3339
    3440=== version ===
    35 you should set `version`, but `milestone` can be left to developers
     41Setting `version` is recommended, but `milestone` can be left to developers
    3642
    3743=== description ===
    3844
    39 Explain how to reproduce the problem. Check if you can see it in the samples. If not, modify one of the samples to demonstrate it and attach a patch.
     45Explain how to reproduce the problem. Check if you can see it in the samples. If not, try to modify one of the samples to demonstrate it and attach the modification as a patch.
     46
     47If you use wxPython and can show the program in a few lines of Python code, that's also useful. Make sure the code is '''complete''' (with imports and instantiation of `wx.PySimpleApp()`)
     48and '''minimal'''.
    4049
    4150=== final note ===
    42 At last, when you see that the bug you reported in the past was fixed, but the ticket is still open, we will appreciate if you close it.
     51At last, when you see that the bug you reported in the past was fixed, but the ticket is still open, we will appreciate if you close it. You can easily list [query:status!=closed&reporter=$USER&group=componentall open bugs you reported]
    4352And at any time, feel free to verify other bugs in the tracker.
    4453