Merge commit 'b146d74730ab9ec5abede9066f770ad851e45fbc'

[ffmpeg] / doc / developer.texi

diff --git a/doc/developer.texi b/doc/developer.texi
index 96e77aeaf2ff60ebb9f60b9069c1268a968be8d7..cd635a81611f0d1353df70ee91c4eb5be804c896 100644 (file)
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -394,6 +394,8 @@ send a reminder by email. Your patch should eventually be dealt with.
     Did you register it in @file{allcodecs.c} or @file{allformats.c}?
 @item
     Did you add the AVCodecID to @file{avcodec.h}?
+    When adding new codec IDs, also add an entry to the codec descriptor
+    list in @file{libavcodec/codec_desc.c}.
 @item
     If it has a fourCC, did you add it to @file{libavformat/riff.c},
     even if it is only a decoder?
@@ -533,4 +535,16 @@ Running 'make fate' accomplishes this, please see @url{fate.html} for details.
 this case, the reference results of the regression tests shall be modified
 accordingly].
 
+@subsection Adding files to the fate-suite dataset
+
+When there is no muxer or encoder available to generate test media for a
+specific test then the media has to be inlcuded in the fate-suite.
+First please make sure that the sample file is as small as possible to test the
+respective decoder or demuxer sufficiently. Large files increase network
+bandwidth and disk space requirements.
+Once you have a working fate test and fate sample, provide in the commit
+message or introductionary message for the patch series that you post to
+the ffmpeg-devel mailing list, a direct link to download the sample media.
+
+
 @bye