Guideline for creating issues » History » Version 10
« Previous -
Next » -
Leonid Protasov, 02/17/2014 05:45 PM
Guideline/Rules for creating issues¶
- Before reporting a bug be sure you updated to the latest Bleeding edge version: https://showtimemediacenter.com/downloads/showtime/master
- If it's a bug - attach the log: https://showtimemediacenter.com/projects/showtime/wiki/Logging
- Don't reuse bugs. If a bug has been closed and it's not the exact same issue, file a new bug.
- 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.
- Unless you know that the bug is a regression (ie, something that worked fine in a previous version of Showtime), please try using the latest version of Showtime before filing the bug. The official versions are found here. If you are using your own builds or builds from somewhere else you better be sure what you are doing.
- 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 > 500 MB (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 count=50to generate a 50MB file
- If you are worried about attaching sensitive material to a ticket, make the ticket private (available when the ticket is created). By doing so only a small set of trusted developers (currently two people) will be able to access the contents.
Failure to comply with these (simple) rules will result in the issue being rejected. If you think 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,