[FFmpeg-devel] [RFC] FFmpeg 3.3
michael at niedermayer.cc
Fri Mar 31 21:19:02 EEST 2017
On Fri, Mar 31, 2017 at 03:07:15PM +0200, Michael Niedermayer wrote:
> On Fri, Mar 31, 2017 at 01:31:51PM +0200, Michael Niedermayer wrote:
> > On Tue, Mar 14, 2017 at 12:29:52PM +0100, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > are there any issues/tickets that block making 3.3 ?
> > >
> > > What about the spherical API size_t / uint32_t issue ?
> > > we can change it before the release but not after it
> > Ive finally branched release/3.3 off
> > feel free to backport anything
> > we also need release notes and all that stuff
> > once we all agree ill make 3.3 from it
> wm4 and ubitux stated on irc that now is a bad time to release due to
> the many recent merges
> so what shall we do ?
> should we release now (as in a few days) anyway ?
> should we wait till the merge rate slows down ? (no idea when that will
> be or in what condition the tree will then be)
> should we make a 3.3 release from 0bab78f7e729a76ea7a8cbec7f1de033c52494e8
> that is 3 weeks ago with backports ?
heres 0bab78f7e729a76ea7a8cbec7f1de033c52494e8 with commits backported
till master of today ommiting merges, anything changing version (cant be
backported due to conflicting version numbers), most hwaccel stuff
(as likely related to merges), most cherry picks from libav and
anything that didnt apply / depended on ommited commits
fate of course passes
do people prefer this over what is in release/3.3 ?
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: Digital signature
More information about the ffmpeg-devel