Project

General

Profile

Issue Tracker Guidelines » History » Version 4

I. Lazaridis, 03/25/2014 03:21 PM

1 1 I. Lazaridis
h1. Issue Tracker Guidelines
2
3
4
h2. Scope
5
6
The main scope of the Issue Tracker is to assist wt developers in their daily work, and to provide the users of wt the means for precise feedback on wt.
7
8
9
h2. Developers
10
11 4 I. Lazaridis
* Do not reject issues immediately, except you are 100% sure. It can make the project look rude and more.
12
** Another user can find the open issue (e.g. a feature request) and suggest a way to implement it.
13 1 I. Lazaridis
** See e.g. #2857, the developer should have asked additionally for the reasons, instead of "rejecting" immediately.
14
* Do not leave old issues (e.g. older than a year) unprocessed.
15
16
h2. Users
17
18 2 I. Lazaridis
* You file new Issues with the "New issue":/projects/wt/issues/new entry in the main menu
19 1 I. Lazaridis
* Create an account, thus you have the benefit of having a list of your issues.
20
* Express yourself clearly and give context and version information 
21
* If your issue was closed or rejected, do not file a new one
22
** You can still comment on a closed/rejected issue.
23
** You can open a topic on the forum and discuss the issue with other users.
24
* File one Issue for each Bug/Feature/Request you have (do not combine them)
25 3 I. Lazaridis
** Negative Example: #2856
26 1 I. Lazaridis
* If you are not sure, open a topic on the forum and discuss your issue.