1 FFmpeg's bug/patch/feature request tracker manual
2 =================================================
8 FFmpeg uses Roundup for tracking issues, new issues and changes to
9 existing issues can be done through a web interface and through email.
10 It is possible to subscribe to individual issues by adding yourself to the
11 nosy list or to subscribe to the ffmpeg-issues mailing list which receives
12 a mail for every change to every issue. Replies to such mails will also
13 be properly added to the respective issue.
14 (the above does all work already after light testing)
15 The subscription URL for the ffmpeg-issues list is:
16 http://live.polito/mailman/listinfo/ffmpeg-issues
17 The URL of the webinterface of the tracker is:
18 http(s)://roundup.mplayerhq/roundup/ffmpeg/
19 Note the URLs in this document are obfuscated, you must append the top level
20 domain of Hungary to the tracker, and of Italy to the mailing list.
24 There is a mailing list to which all new issues and changes to existing issues
25 are sent. You can subscribe through
26 http://live.polito/mailman/listinfo/ffmpeg-issues
27 Replies to messages there will have their text added to the specific issues.
28 Attachments will be added as if they had been uploaded via the web interface.
29 You can change the status, substatus, topic, ... by changing the subject in
31 Re: [issue94] register_avcodec and allcodecs.h [type=patch;status=open;substatus=approved]
32 Roundup will then change things as you requested and remove the [...] from
33 the subject before forwarding the mail to the mailing list.
36 NOTE: issue = (bug report || patch || feature request)
41 An error, flaw, mistake, failure, or fault in FFmpeg or libav* that
42 prevents it from behaving as intended.
45 Request of support for encoding or decoding of a new codec, container
47 Request of support for more, less or plain different output or behavior
48 where the current implementation cannot be considered wrong.
51 A patch as generated by diff which conforms to the patch submission and
58 Bugs and patches which deal with data loss and security issues.
59 No feature request can be critical.
62 Bugs which make FFmpeg unusable for a significant number of users, and
64 Examples here might be completely broken MPEG-4 decoding or a build issue
66 While broken 4xm decoding or a broken OS/2 build would not be important,
67 the separation to normal is somewhat fuzzy.
68 For feature requests this priority would be used for things many people
75 Bugs and patches about things like spelling errors, "mp2" instead of
76 "mp3" being shown and such.
77 Feature requests about things few people want or which do not make a big
81 Something that is desirable to have but that there is no urgency at
82 all to implement, e.g. something completely cosmetic like a website
83 restyle or a personalized doxy template or the FFmpeg logo.
84 This priority is not valid for bugs.
99 Type/Status/Substatus:
102 Initial state of new bugs, patches and feature requests submitted by
106 Issues which have been briefly looked at and which did not look outright
108 This implicates that no real more detailed state applies yet. Conversely,
109 the more detailed states below implicate that the issue has been briefly
113 Bugs, patches or feature requests which are duplicates.
114 Note that patches dealing with the same thing in a different way are not
116 Note, if you mark something as duplicate, do not forget setting the
117 superseder so bug reports are properly linked.
120 Bugs caused by user errors, random ineligible or otherwise nonsense stuff.
122 */closed/needs_more_info
123 Issues for which some information has been requested by the developers,
124 but which has not been provided by anyone within reasonable time.
127 Bugs which have been reproduced.
130 Bugs which have been analyzed and where it is understood what causes them
131 and which exact chain of events triggers them. This analysis should be
132 available as a message in the bug report.
133 Note, do not change the status to analyzed without also providing a clear
134 and understandable analysis.
135 This state implicates that the bug either has been reproduced or that
136 reproduction is not needed as the bug is already understood.
138 bug/open/needs_more_info
139 Bug reports which are incomplete and or where more information is needed
140 from the submitter or another person who can provide it.
141 This state implicates that the bug has not been analyzed or reproduced.
142 Note, the idea behind needs_more_info is to offload work from the
143 developers to the users whenever possible.
146 Bugs which have to the best of our knowledge been fixed.
149 Bugs which we will not fix, the reasons here could be legal, philosophical
152 bug/closed/works_for_me
153 Bugs for which sufficient information was provided to reproduce but
154 reproduction failed - that is the code seems to work correctly to the
155 best of our knowledge.
158 Patches which have been reviewed and approved by a developer.
159 Such patches can be applied anytime by any other developer after some
160 reasonable testing (compile + regression tests + does the patch do
161 what the author claimed).
163 patch/open/needs_changes
164 Patches which have been reviewed and need changes to be accepted.
167 Patches which have been applied.
169 patch/closed/rejected
170 Patches which have been rejected.
172 feature_request/open/needs_more_info
173 Feature requests where it is not clear what exactly is wanted
174 (these also could be closed as invalid ...).
176 feature_request/closed/implemented
177 Feature requests which have been implemented.
179 feature_request/closed/wont_implement
180 Feature requests which will not be implemented. The reasons here could
181 be legal, philosophical or others.
183 Note, please do not use type-status-substatus combinations other than the
184 above without asking on ffmpeg-dev first!
186 Note2, if you provide the requested info do not forget to remove the
187 needs_more_info substate.
191 A topic is a tag you should add to your issue in order to make grouping them
195 issues in libavcodec/*
198 issues in libavformat/*
201 issues in libavutil/*
207 issues in or related to ffmpeg.c
210 issues in or related to ffplay.c
213 issues in or related to ffserver.c
216 issues in or related to configure/Makefile
219 bugs which were working in a past revision
222 issues related to our issue tracker