On Wed, 20 Aug 2014 17:35:23 +0200, Diego Biurrun <[email protected]> wrote: > On Mon, Aug 18, 2014 at 06:04:47PM +0000, Anton Khirnov wrote: > > --- a/doc/RELEASE_NOTES > > +++ b/doc/RELEASE_NOTES > > @@ -1,51 +1,47 @@ > > > > +strongly discouraged and will likely be deprecated in the future. The users > > +should instead allocate a separate decoding or encoding context and > > populate it > > Users should instead allocate > > > +The main highlights of this release include native Opus, VP7, On2 AVC or > > OpenEXR > > s/or/and/ > > > +decoder, HEVC encoding through libx265, new APIs for exporting ReplayGain > > and > > decoderS > > > +display transformation metadata and countless bugfixes. A large effort was > > also > > +expended on internal cleanups, which are not very visible to our users, but > > +should make the codebase cleaner, safer and easier to maintain and extend. > > Maybe mention dsputil explicitly? > > > -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. > > +The avserver streaming tool, which has not been maintained for many years > > and > > +was mostly broken, was removed from the tree. It was decided that it is a > > +significant maintenance burden and that we do our users no service by > > pretending > > +to support it, while we in fact do not. > > Shall we remove that paragraph about bug reports? I don't particularly mind. >
Well, it's not true anymore. We do accept bugreports for stable branches these days. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
