[x265] Poor Development Practices

[Steve Borho]

On Tue, Feb 18, 2014 at 12:59 PM, Derek Buitenhuis <
derek.buitenhuis at gmail.com> wrote:

> On 2/18/2014 6:36 PM, Steve Borho wrote:
> > So when I bump X265_BUILD, ffmpeg will no longer try to compile against
> x265 until it is patched?  How does this work in practice?  Should I be
> sending patches for ffmpeg/libav when we change API?
>
> I can currently lock it into a version range. Right now it just checks
> for X265_BUILD >= 5.
>
> The way so far with libx264 has been to bump the minimum required build.
>
> I hope the x265 API is not too volatile -- I don't think people over at
> Libav
> and FFmpeg will like me submitting weekly patches for API breakage.


Understood.

We can certainly batch up API changes so we do them very infrequently; but
I don't see any more changes necessary for the current batch of feature
work.  4:2:2 is covered, and so is VBV.

-- 
Steve Borho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20140218/82873059/attachment.html>