Guideline for creating issues » History » Version 3
Andreas Smas, 05/28/2011 09:55 PM
h1. Guideline/Rules for creating issues
* Don't create duplicate bugs. At least try to skim the list before posting a new one.
* For bugs: Always write the version where the bug is found. There is a specific field for that. This does not apply for features.
* Don't write multiple bugs/feature requests, etc in one single ticket. It's harder to discuss and know when things are done.
* 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.
* 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.
** On Windows use this tool: http://www.filesplitter.org/
** On Linux use the *dd* command: @dd if=<originalfile> of=cut.mkv bs=1000000 [email protected] to generate a 50MB file
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.
Thank you for understanding,