Add a part explaining that API should be considered unstable after major
[libav.git] / doc / APIchanges
1 Never assume the API of libav* to be stable unless at least 1 week has passed since
2 the last major version increase.
3 The last version increases were:
4 libavcodec: ?
5 libavdevice: ?
6 libavfilter: ?
7 libavformat: ?
8 libpostproc: ?
9 libswscale: ?
10 libavutil: 2009-03-08
11
12
13 API changes, most recent first:
14
15 20090308 - r17869 - lavu 50.0.0 - AVFifoBuffer
16 av_fifo_init, av_fifo_read, av_fifo_write and av_fifo_realloc were dropped and replaced
17 by av_fifo_alloc, av_fifo_generic_read, av_fifo_generic_write and av_fifo_realloc2.
18 The AVFifoBuffer/struct AVFifoBuffer may only be used in an opaque way by applications,
19 they may not use sizeof() or directly access members.
20
21 20090301 - r17682 - lavf 52.31.0 - Generic metadata API
22 This version introduces a new metadata API (see av_metadata_get() and friends).
23 The old API is now deprecated and shouldn't be used anymore. This especially
24 includes the following structure fields:
25 - AVFormatContext.title
26 - AVFormatContext.author
27 - AVFormatContext.copyright
28 - AVFormatContext.comment
29 - AVFormatContext.album
30 - AVFormatContext.year
31 - AVFormatContext.track
32 - AVFormatContext.genre
33 - AVStream.language
34 - AVStream.filename
35 - AVProgram.provider_name
36 - AVProgram.name
37 - AVChapter.title