[FFmpeg-devel] FFmpeg 3.5 / 4.0

[Paul B Mahol]

On 4/18/18, wm4 <nfxjfg at googlemail.com> wrote:
> On Wed, 18 Apr 2018 23:15:47 +0200
> Michael Niedermayer <michael at niedermayer.cc> wrote:
>
>> On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote:
>> > On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer
>> > <michael at niedermayer.cc> wrote:
>> > > On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote:
>> > >> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote:
>> > >>
>> > >> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer
>> > >> > wrote:
>> > >> > > Hi
>> > >> > >
>> > >> > > Its 4 months since 3.4 was branched so its time for a new major
>> > >> > > release
>> > >> > >
>> > >> > > Is 4.0 or 3.5 preferred ?
>> > >> > > Any name suggestions ?
>> > >> > >
>> > >> > > If there are no objections i will likely make that release in the
>> > >> > > next weeks
>> > >> >
>> > >> > more time has passed than intended ...
>> > >> >
>> > >> > what issues do remain that need to be fixed before the release ?
>> > >> > I see fate.ffmpeg.org is not looking that well (compared to most
>> > >> > releases in the past) i remember this being pretty much green
>> > >> > longer ago
>> > >> > do people want these to be fixed before the release ?
>> > >>
>> > >> ok, so, my plan is to create a release/4.0 branch from master in the
>> > >> next
>> > >> 24-48 hours unless theres some issue brought to my attention (CC me
>> > >> just to
>> > >> be sure if theres an issue)
>> > >>
>> > >> then wait 2 days or so and backport any newly found bugfixes to
>> > >> release/4.0
>> > >> and then make the release finally
>> > >>
>> > >> delays at any point are possible due to issues, lack of time or
>> > >> other.
>> > >>
>> > >> as name i think kierans suggestion of Wu would make sense. IIRC we
>> > >> had
>> > >> no name suggested by more than 1 developer. Please correct me if i
>> > >> miscounted i did only briefly re-check the mails in the thread.
>> > >
>> > >
>> > > release/4.0 branched
>> > > next is the release in a few days.
>> > > If theres something i should wait for please say so and CC me
>> > > also please backport all bugfixes to 4.0
>> >
>> > I have two more fixes that should really go in 4.0, one is the
>> > tls_schannel fix that I plan to push soon (I'm the author of that
>> > module, so unless someone says otherwise soon), and the MSVC configure
>> > breakage introduced in the last 2 days.
>> > Not sure when you planned to tag, but hopefully both of those are
>> > resolved by tomorrow afternoon.
>>
>> well i had a bad headache today and iam a bit behind now with stuff
>> so i likely wont be ready before tomorrow evening either.
>
> Please also wait with the release until we've sorted out the general
> avio EOF mess.

No, that need to wait 5.0