summaryrefslogtreecommitdiff
path: root/doc/RELEASE_NOTES
diff options
context:
space:
mode:
Diffstat (limited to 'doc/RELEASE_NOTES')
-rw-r--r--doc/RELEASE_NOTES36
1 files changed, 14 insertions, 22 deletions
diff --git a/doc/RELEASE_NOTES b/doc/RELEASE_NOTES
index 8c642b9e4d..ad4279cc82 100644
--- a/doc/RELEASE_NOTES
+++ b/doc/RELEASE_NOTES
@@ -1,23 +1,14 @@
Release Notes
=============
-* 0.8 "Forbidden Fruit"
+* 0.9 "Harmony" December, 2011
+
General notes
-------------
-
-This release continues the API cleanups that have begun with the
-previous release. While it is binary compatible with 0.7, many parts of
-the public API were deprecated and will be removed in the git master and
-later releases. Please consult the doc/APIchanges file to see
-intended replacements for the deprecated APIs.
-
-Furthermore, our work on the 'ffmpeg' command-line tool has resulted in
-major revisions to its interface. In order to not break existing scripts
-and applications, we have chosen to introduce a new tool called
-'avconv', and keep the traditional 'ffmpeg' frontend for end-user's
-convenience. Please see the Changelog file for details how 'avconv'
-differs from 'ffmpeg'.
+This release is binary compatible with 0.8. The 'ffmpeg' command-line tool has
+been extended to also support the command line syntax and features of a tool
+called avconv.
Additionally, this release introduces a number of new interesting codecs
such as the Apple Prores, Flash Screen Video 2 and Windows Media Image,
@@ -25,13 +16,14 @@ and muxers such as LATM or CELT in Ogg, among many others. Moreover, our
H.264 decoder has been improved to decode 4:2:2 material and our libx264
wrapper now allows to produce 4:2:2 and 4:4:4 video.
-See the Changelog file for a list of significant changes.
+See the Changelog file for a list of significant changes. Note, there
+are many more new features and bugfixes than whats listed there.
-Please note that our policy on bug reports has not changed. We still only accept
-bug reports against HEAD of the Libav trunk repository. If you are experiencing
-issues with any formally released version of Libav, please try a current version
-of the development code to check if the issue still exists. If it does, make your
-report against the development code following the usual bug reporting guidelines.
+Bugreports against FFmpeg git master or the most recent FFmpeg release are
+accepted. If you are experiencing issues with any formally released version of
+FFmpeg, please try git master to check if the issue still exists. If it does,
+make your report against the development code following the usual bug reporting
+guidelines.
API changes
@@ -76,7 +68,7 @@ are, in order of preference:
1) Try finding a way of accomplishing the same with public API.
2) If there is no corresponding public API, but you think there should be,
post a request on the user mailing list or IRC channel.
-3) Finally if your program needs access to Libav internals for some special
-reason then the best solution is to link statically.
+3) Finally if your program needs access to FFmpeg / libavcodec / libavformat
+internals for some special reason then the best solution is to link statically.
Please see the Changelog file for a more detailed list of changes.