From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 9FC7447711 for ; Wed, 20 Sep 2023 17:24:20 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 0EC1168C7E1; Wed, 20 Sep 2023 20:24:18 +0300 (EEST) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 06B2968C6F8 for ; Wed, 20 Sep 2023 20:24:10 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 35B69C0005 for ; Wed, 20 Sep 2023 17:24:09 +0000 (UTC) Date: Wed, 20 Sep 2023 19:24:07 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20230920172407.GJ8640@pb2> References: <20230410221428.GJ1164690@pb2> <20230919191803.GB35669@haasn.xyz> <20230919191608.GE8640@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] FFmpeg release 6.1 X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============7056640326509292361==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============7056640326509292361== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ensexbfp9Ul6anXl" Content-Disposition: inline --ensexbfp9Ul6anXl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 19, 2023 at 11:58:41PM +0200, Lynne wrote: > Sep 19, 2023, 21:16 by michael@niedermayer.cc: >=20 > > On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote: > > > >> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer wrote: > >> > Hi all > >> >=20 > >> > There was the request to make a 6.1 before end of April > >> > Is that still so ? > >> >=20 > >> > 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 th= is > > 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 patch= es > > going back and forth on these and discussing with tech/community commit= ttees > > also took time. > > And last but not least if people want me to design a standalone SDR lib= rary > > 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 ca= re > > > > Also I did fall behind with security fixes in the summer a bit, the wea= ther 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 th= at 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 fas= ter > > > > I also have some paid work under NDA which i signed a contract for, i n= eed > > to work on that too. Yes code will be submitted to FFmpeg when/if its d= one > > 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 no= t 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 q= uick > > as I and others wanted > > > > thx > > > > [...] > > --=20 > > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > > > If you think the mosad wants you dead since a long time then you are ei= ther > > wrong or dead since a long time. > > >=20 > 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 dont suggest merging more EVC code before the release. I meant the EVC code already in git, is reading alot of things with no checks. It maybe doesnt matter in most cases, as its not used in most cases without more EVC code but still Also ATM other things are blocking so EVC still could make it in principle. Just that the release should not be delayed because of addition of more EVC= code But someone needs to check the existing EVC code in git without checks is s= afe >=20 > I'd like to get my AAC padding/duration fixes in, and drop lavc's > old FFT code entirely. fine thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong. --ensexbfp9Ul6anXl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZQsqsAAKCRBhHseHBAsP q/ikAJ4yYpH95HOeuR6w0O/P/RM9q8/GogCfc0fftQcOcMdJmkLC+/3Cl8XGpUQ= =URrd -----END PGP SIGNATURE----- --ensexbfp9Ul6anXl-- --===============7056640326509292361== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============7056640326509292361==--