[mythtv] FFmpeg plans

David Engel david at istwok.net
Mon Apr 30 15:45:07 UTC 2018


On Sun, Apr 29, 2018 at 04:44:53PM -0400, Peter Bennett wrote:
> 
> 
> On 04/29/2018 04:08 PM, David Engel wrote:
> > Likewise, I'm not sure that FFmpeg's master branch is the best choice.
> > How do you propose to handle post-release fixes from FFmpeg?  Looking
> > at FFmpeg's release branch for 3.4, it saw a lot of fixes spanning 4
> > months after the initial releases.  Perhaps Aman could shed some light
> > on how FFmpeg handles their release and master branches and suggest
> > the best one to track.
> Hi David
> 
> I looked at https://ffmpeg.org/download.html#get-sources
> They recommend in two places there that people compiling from source should
> use the development (master) branch. They also state that fixes are first
> applied to master and then some of them are cherry-picked into release
> branches.

That recommendation seems highly unusual to me.  Why do releases at
all then?  It sounds like thay handle release branches in the same,
pretty standard way we do.  We try to keep our master branch stable
too, but we don't recommend others run it.  I wonder why they do.

David

> If we use a release branch, I do not know if the subtree approach will work.
> When we move from one release branch to the next release branch, I don't
> know if pulling from a different branch would work.
> 
> Also, regarding post-release fixes, AFAIK we currently do not take them. I
> have not merged in any post-release fixes for 3.4. If we use master we can
> do another pull any time to get fixes.
> 
> Peter
> 

-- 
David Engel
david at istwok.net


More information about the mythtv-dev mailing list