Guideline for creating issues » History » Version 3

Andreas Smas, 05/28/2011 09:55 PM

1 1 Andreas Smas
h1. Guideline/Rules for creating issues
2 1 Andreas Smas
3 3 Andreas Smas
* Don't create duplicate bugs. At least try to skim the list before posting a new one.
4 3 Andreas Smas
5 2 Andreas Smas
* For bugs: Always write the version where the bug is found. There is a specific field for that. This does not apply for features.
6 1 Andreas Smas
7 1 Andreas Smas
* Don't write multiple bugs/feature requests, etc in one single ticket. It's harder to discuss and know when things are done.
8 1 Andreas Smas
9 1 Andreas Smas
* If a file is unplayable for whatever reason you must attach a sample of it or it is almost impossible for me to figure out what's wrong.
10 1 Andreas Smas
11 1 Andreas Smas
* If the sample file is bigger than >250Meg (it usually is for movies) the file can just be cut into pieces. 50Mb should be enough. This does not work for all fileformats  but for AVI and MKV it should work fine.
12 1 Andreas Smas
** On Windows use this tool:
13 1 Andreas Smas
** On Linux use the *dd* command: @dd if=<originalfile> of=cut.mkv bs=1000000 [email protected] to generate a 50MB file
14 1 Andreas Smas
15 1 Andreas Smas
Failure to comply with these (simple) rules will result in the issue being rejected. If you thing that's unfair for me to impose these rules consider the amount of time I've spend on the project so far. Badly written tickets will just consume more of my time that I could spend on new features instead.
16 1 Andreas Smas
17 1 Andreas Smas
Thank you for understanding,
18 1 Andreas Smas