On Wed, Apr 15, 2020 at 8:14 AM James Almer <jamr...@gmail.com> wrote: > > On 4/14/2020 9:26 PM, James Zern wrote: > > On Tue, Apr 14, 2020 at 3:57 AM Ryo Hirafuji <ryo.hiraf...@link-u.co.jp> > > wrote: > >> > >> Thanks for the review! > >> > >> This should bump the micro version number in libavcodec/version.h. > >> > >> > >> OK, I will bump up the version when the problem below is solved. > >> > > > > If we want to go for compatibility with different versions of the > > library we could move forward with the patch as is, though it would be > > simpler to just treat this as a bug fix in libaom. > > Once a new version of libaom is tagged (Hopefully soon, since it's been > almost two years since 1.0.0), we could set it as the minimum > requirement and forget about 1.0.0, since that version is by now > essentially unusable. >
Thanks, that was my hope. I just wasn't sure how long we wanted to wait before changing the minimum. You're right though, the only tags are old and were more for bitstream compatibility rather than encoder functionality. A full release should be coming soon [1] and with more regular frequency after that. [1] https://crbug.com/aomedia/2545 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
