From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg release 6.1
Date: Tue, 19 Sep 2023 23:58:41 +0200 (CEST)
Message-ID: <NejRxyY--3-9@lynne.ee> (raw)
In-Reply-To: <20230919191608.GE8640@pb2>
Sep 19, 2023, 21:16 by michael@niedermayer.cc:
> On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
>
>> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer <michael@niedermayer.cc> wrote:
>> > Hi all
>> >
>> > There was the request to make a 6.1 before end of April
>> > Is that still so ?
>> >
>> > Assuming it is, its time to make that branch and release soon
>>
>> Hi,
>>
>> It is now september. What happened to this release? FFmpeg 6.1 is
>> currently the only thing blocking the adoption of vulkan video.
>>
>
> there are several security issues that need to be fixed
> ossfuzz found more, it also put some random unlreated issues again
> into the same ticket. (which are basically invissible sub-tickets)
> the evc code also needs a security review, Maybe Dawid is working on this
> iam not sure. And iam sure theres more
> We also have a security issue in fate, i belive nicolas is looking into
> that, that doesnt hold up the release but all these things compete for time
> and some people you may have noticed tried to just randomly block patches
> going back and forth on these and discussing with tech/community committtees
> also took time.
> And last but not least if people want me to design a standalone SDR library
> while thats not holding up 6.1 it takes time from the pot from 6.1 work.
> I did say this, i was attacked but yes time is unforgiving it doesnt care
>
> Also I did fall behind with security fixes in the summer a bit, the weather was
> nice, some members of the community where not nice. So i tried to spend some
> time with the nice weather
>
> If you want 6.1 to happen quick. be nice to me or help with anything that i
> have to work on 6.1 or other so theres more time in the pot
> what about merging libplacebo into FFmpeg for example ?
> As far as iam concerned you can have absolute final power about anything
> in that libplacebo inside FFmpeg.
> Or help with the whole SDR thing. If i dont have to think about it and
> can concentrate on the release and security then yes it will happen faster
>
> I also have some paid work under NDA which i signed a contract for, i need
> to work on that too. Yes code will be submitted to FFmpeg when/if its done
> And theres life, i have other shit to do too. For example my taxes and i also
> want to spend some time working on AI/neural nets. I guess that will not be
> FFmpeg related as id like my work on AI not to be in a similar position to
> where avradio is now.
>
> So yeah, i think theres no problem with 6.1 its just not happening as quick
> as I and others wanted
>
> thx
>
> [...]
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> If you think the mosad wants you dead since a long time then you are either
> wrong or dead since a long time.
>
I'm not sure it's a good idea to wait to merge the EVC decoder.
Perhaps we should move that to the next release.
I'd like to get my AAC padding/duration fixes in, and drop lavc's
old FFT code entirely.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-09-19 21:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 22:14 Michael Niedermayer
2023-04-10 22:16 ` James Almer
2023-04-11 8:46 ` Neal Gompa
2023-09-19 17:18 ` Niklas Haas
2023-09-19 19:16 ` Michael Niedermayer
2023-09-19 21:58 ` Lynne [this message]
2023-09-20 0:38 ` Neal Gompa
2023-09-20 2:24 ` Xiang, Haihao
2023-09-20 17:24 ` Michael Niedermayer
2023-09-20 17:43 ` Kieran Kunhya
2023-09-20 18:10 ` Michael Niedermayer
2023-09-20 22:47 ` Kieran Kunhya
2023-09-21 3:19 ` Jean-Baptiste Kempf
2023-09-21 12:51 ` Michael Niedermayer
2023-09-20 12:47 ` Niklas Haas
2023-09-20 18:00 ` Michael Niedermayer
2023-09-21 11:46 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-09-21 16:21 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Michael Niedermayer
2023-09-21 16:33 ` Kieran Kunhya via ffmpeg-devel
2023-09-21 17:16 ` Nicolas George
2023-09-21 18:14 ` Vittorio Giovara
2023-09-21 18:19 ` Nicolas George
2023-09-21 18:47 ` Vittorio Giovara
2023-09-21 18:51 ` Nicolas George
2023-09-21 18:54 ` Vittorio Giovara
2023-09-21 19:04 ` Nicolas George
2023-09-21 19:08 ` Paul B Mahol
2023-09-26 18:14 ` Nicolas George
2023-09-21 19:18 ` Vittorio Giovara
2023-09-21 19:37 ` Nicolas George
2023-09-21 19:44 ` Paul B Mahol
2023-09-21 18:56 ` Michael Niedermayer
2023-09-26 19:59 ` Rémi Denis-Courmont
2023-09-21 16:39 ` Paul B Mahol
2023-09-22 13:55 ` Gijs Peskens
2023-09-22 16:32 ` Michael Niedermayer
2023-09-23 6:49 ` Neal Gompa
2023-09-23 10:55 ` Michael Niedermayer
2023-09-23 23:31 ` Neal Gompa
2023-09-24 9:12 ` Nicolas George
2023-09-24 11:56 ` Paul B Mahol
2023-09-24 12:17 ` Nicolas George
2023-09-24 17:33 ` Paul B Mahol
2023-09-24 17:45 ` [FFmpeg-devel] libavdevice (was: FFmpeg release 6.1 (SDR Plans)) Nicolas George
2023-09-24 17:49 ` Paul B Mahol
2023-09-24 17:54 ` Nicolas George
2023-09-24 18:05 ` Paul B Mahol
2023-09-24 18:09 ` Nicolas George
2023-09-25 11:20 ` Paul B Mahol
2023-09-26 18:12 ` Nicolas George
2023-09-25 8:24 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Kieran Kunhya
2023-09-26 20:17 ` Rémi Denis-Courmont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NejRxyY--3-9@lynne.ee \
--to=dev@lynne.ee \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git