Changes between Version 4 and Version 5 of ReportingBugs
- Timestamp:
- 01/08/13 15:05:56 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReportingBugs
v4 v5 1 1 = Reporting Bugs = 2 2 3 [[BR]] 4 5 6 == Guidelines == 3 7 If you are reporting a bug, it generally means that you want something investigated and changes to take place. If you have not read it yet, please take a moment to read [http://www.catb.org/esr/faqs/smart-questions.html#beprecise Smart Questions] - it is a very good read and will be helpful to you well beyond the scope of this project. 4 8 … … 16 20 * does re-connecting help? 17 21 * does it happen with other type of clients (different OS, etc) 22 * The [/wiki/Debugging debugging instructions] can be used to add a lot more detailed information 18 23 19 24 The best way to ensure that the information is clear and detailed is often to just paste the command lines used to get the information directly. ie: rather than saying "I have the latest version installed" (which by definition, changes all the time), paste something like this: … … 28 33 29 34 OK, now feel free to [/newticket file a bug]. 35 36 == Login required due to spam - sorry! == 37 Due to the high level of trac spam, you must [/register register] to create new tickets. Sorry. 38 [[BR]] 39 It will ask you to provide an email address to verify your account. In case you lose the link, the verification page is [/verify_email here] 40 [[BR]] 41 Note: if you do not get the email within 5 minutes, check you spam folder.. If it still fails contact us: {{{xpra@devloop.org.uk}}} 42 [[BR]] 43 Your email address will not be used for anything else, and will not be passed on to anyone, for any reason.