[Ffmpeg-cvslog] CVS: ffmpeg/doc ffmpeg-doc.texi,1.104,1.105

Diego Biurrun diego
Sat Jan 14 15:41:47 CET 2006

On Sat, Jan 14, 2006 at 10:26:00AM +0100, Reimar D?ffinger wrote:
> On Sat, Jan 14, 2006 at 02:31:25AM +0100, Diego Biurrun CVS wrote:
> > + at item
> > +    If you add a new codec, remember to update the changelog, add it to the
> > +    supported codecs table and bump the version number appropriately.
> Maybe say which part of the version number should be bumped, because
> that's the only part I did not yet have in my local tree (if there is
> already a description of the numbering scheme somewhere just refering to
> it would be okay, too).

It's described just above:

    Remember to check if you need to bump versions for the specific
    libav parts (libavutil, libavcodec, libavformat) you are changing.
    You need to change the version integer and the version string.
    Incrementing the first component means no backward compatibility to
    previous versions (e.g. removal of a function). Incrementing the
    second component means backward compatible change (e.g. addition of
    a function). Incrementing the third component means a noteworthy
    binary compatible change (e.g. encoder bug fix that matters for the

I discussed this with Roberto, he said that adding a codec warrants
incrementing the second component.

> I would also add that if it is a codec with fourcc, it must be added
> to libavformat/avienc.c, even if it is only a decoder (IMHO good hint
> for people like me where ffmpeg support is just an afterthought.

Yes, good point.


More information about the ffmpeg-cvslog mailing list