diff options
Diffstat (limited to 'ffmpeg/doc/issue_tracker.txt')
| -rw-r--r-- | ffmpeg/doc/issue_tracker.txt | 61 |
1 files changed, 21 insertions, 40 deletions
diff --git a/ffmpeg/doc/issue_tracker.txt b/ffmpeg/doc/issue_tracker.txt index d487f66..33b3535 100644 --- a/ffmpeg/doc/issue_tracker.txt +++ b/ffmpeg/doc/issue_tracker.txt @@ -1,4 +1,4 @@ -FFmpeg's bug/patch/feature request tracker manual +FFmpeg's bug/feature request tracker manual ================================================= NOTE: This is a draft. @@ -11,7 +11,7 @@ existing issues can be done through a web interface. Issues can be different kinds of things we want to keep track of but that do not belong into the source tree itself. This includes -bug reports, patches, feature requests and license violations. We +bug reports, feature requests and license violations. We might add more items to this list in the future, so feel free to propose a new `type of issue' on the ffmpeg-devel mailing list if you feel it is worth tracking. @@ -24,10 +24,13 @@ a mail for every change to every issue. The subscription URL for the ffmpeg-trac list is: http(s)://ffmpeg.org/mailman/listinfo/ffmpeg-trac The URL of the webinterface of the tracker is: -http(s)://ffmpeg.org/trac/ffmpeg +http(s)://trac.ffmpeg.org Type: ----- +art + Artwork such as photos, music, banners, and logos. + bug / defect An error, flaw, mistake, failure, or fault in FFmpeg or libav* that prevents it from behaving as intended. @@ -41,20 +44,18 @@ feature request / enhancement license violation ticket to keep track of (L)GPL violations of ffmpeg by others -patch - A patch as generated by diff which conforms to the patch submission and - development policy. - +sponsoring request + Developer requests for hardware, software, specifications, money, + refunds, etc. Priority: --------- critical - Bugs and patches which deal with data loss and security issues. + Bugs about data loss and security issues. No feature request can be critical. important - Bugs which make FFmpeg unusable for a significant number of users, and - patches fixing them. + Bugs which make FFmpeg unusable for a significant number of users. Examples here might be completely broken MPEG-4 decoding or a build issue on Linux. While broken 4xm decoding or a broken OS/2 build would not be important, @@ -68,7 +69,7 @@ normal minor - Bugs and patches about things like spelling errors, "mp2" instead of + Bugs about things like spelling errors, "mp2" instead of "mp3" being shown and such. Feature requests about things few people want or which do not make a big difference. @@ -103,13 +104,13 @@ This state implicates that the bug either has been reproduced or that reproduction is not needed as the bug is already understood. -Type/Status/Substatus: +Type/Status: ---------- -*/new/new - Initial state of new bugs, patches and feature requests submitted by +*/new + Initial state of new bugs and feature requests submitted by users. -*/open/open +*/open Issues which have been briefly looked at and which did not look outright invalid. This implicates that no real more detailed state applies yet. Conversely, @@ -117,9 +118,7 @@ Type/Status/Substatus: looked at. */closed/duplicate - Bugs, patches or feature requests which are duplicates. - Note that patches dealing with the same thing in a different way are not - duplicates. + Bugs or feature requests which are duplicates. Note, if you mark something as duplicate, do not forget setting the superseder so bug reports are properly linked. @@ -134,7 +133,7 @@ Type/Status/Substatus: bug/closed/fixed Bugs which have to the best of our knowledge been fixed. -bug/closed/wont_fix +bug/closed/wontfix Bugs which we will not fix. Possible reasons include legality, high complexity for the sake of supporting obscure corner cases, speed loss for similarly esoteric purposes, et cetera. @@ -148,33 +147,15 @@ bug/closed/works_for_me reproduction failed - that is the code seems to work correctly to the best of our knowledge. -patch/open/approved - Patches which have been reviewed and approved by a developer. - Such patches can be applied anytime by any other developer after some - reasonable testing (compile + regression tests + does the patch do - what the author claimed). - -patch/open/needs_changes - Patches which have been reviewed and need changes to be accepted. - -patch/closed/applied - Patches which have been applied. - -patch/closed/rejected - Patches which have been rejected. - -feature_request/closed/implemented +feature_request/closed/fixed Feature requests which have been implemented. -feature_request/closed/wont_implement +feature_request/closed/wontfix Feature requests which will not be implemented. The reasons here could be legal, philosophical or others. -Note, please do not use type-status-substatus combinations other than the -above without asking on ffmpeg-dev first! - Note2, if you provide the requested info do not forget to remove the -needs_more_info substatus. +needs_more_info resolution. Component: ---------- |