Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
57492dfe
Commit
57492dfe
authored
Jun 25, 2007
by
Luca Barbato
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Typos removed
Originally committed as revision 9423 to
svn://svn.ffmpeg.org/ffmpeg/trunk
parent
7f63f750
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
12 deletions
+12
-12
issue_tracker.txt
doc/issue_tracker.txt
+12
-12
No files found.
doc/issue_tracker.txt
View file @
57492dfe
ffmpegs bug/patch/feature request tracker manual
================================================
NOTE, this is a draft, its not yet recomm
anded to send real bugrepor
s to the
tracker but rather use the mailinglists
though
if you are brave and dont mind that your bugreport might disa
pear or
that you might be mailbombed due to a mis
sconiguration
you can surely try
NOTE, this is a draft, its not yet recomm
ended to send real bugreport
s to the
tracker but rather use the mailing
lists
though
, if you are brave and don't mind that your bugreport might disap
pear or
that you might be mailbombed due to a mis
configuration,
you can surely try
to enter a real bugreport
Overview:
...
...
@@ -12,7 +12,7 @@ Overview:
FFmpeg uses roundup for tracking issues, new issues and changes to
existing issues can be done through a web interface and through email.
Its possible to subscribe to individual issues by adding yourself to the
nosy list or to subscribe to the ffmpeg-issues mailinglist which receives
nosy list or to subscribe to the ffmpeg-issues mailing
list which receives
a mail for every change to every issue. Replies to such mails will also
properly be added to the respective issue.
(the above does all work already after light testing)
...
...
@@ -43,12 +43,12 @@ critical
no feature request can be critical.
important
Bugs which makes ffmpeg unus
e
able for a significant number of users, and
Bugs which makes ffmpeg unusable for a significant number of users, and
patches fixing them.
examples here might be completly broken mpeg4 decoding or a build issue
examples here might be complet
e
ly broken mpeg4 decoding or a build issue
on linux
while broken 4xm decoding or broken os2 build would not be important, the
sep
e
ration to normal is somewhat fuzzy ...
sep
a
ration to normal is somewhat fuzzy ...
For feature requests this priority would be used for things many people
want.
...
...
@@ -58,11 +58,11 @@ normal
minor
Bugs and patches about things like spelling errors, "mp2" instead of
"mp3" being shown and such
Feature requests about things few people want or which dont make a big
Feature requests about things few people want or which don
'
t make a big
difference.
wish
Something that is desi
de
rable to have but that there is no urgency at
Something that is desirable to have but that there is no urgency at
all to implement, e.g.: something completely cosmetic like a
website restyle or a personalized doxy template or the ffmpeg logo.
This priority isn't valid for bugs.
...
...
@@ -127,7 +127,7 @@ bug/closed/wont_fix
bug/closed/works_for_me
Bugs for which sufficient information was provided to reproduce but
reproduction failed that is the code seems to work correctly to the
best of our knowledg
d
e.
best of our knowledge.
patch/open/approved
Patches which have been reviewed and approved by a developer.
...
...
@@ -152,7 +152,7 @@ feature_request/closed/implemented
Feature requests which have been implemented.
feature_request/closed/wont_implement
Feature reuests which will not be implemented. The reasons here could
Feature re
q
uests 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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment