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 DD8504810F for ; Fri, 10 Nov 2023 01:47:17 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 593DC68CBF3; Fri, 10 Nov 2023 03:47:14 +0200 (EET) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E8C4768CBD6 for ; Fri, 10 Nov 2023 03:47:07 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 41EB31BF203 for ; Fri, 10 Nov 2023 01:47:07 +0000 (UTC) Date: Fri, 10 Nov 2023 02:47:06 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231110014706.GM3543730@pb2> References: <20231028164945.GC3543730@pb2> <20231029045125.GI3543730@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC] 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="===============7591695063026325517==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============7591695063026325517== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="stZPNisUZAOqxp9d" Content-Disposition: inline --stZPNisUZAOqxp9d Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 09, 2023 at 09:20:33AM +0100, Lynne wrote: > Nov 7, 2023, 08:36 by dev@lynne.ee: >=20 > > Oct 29, 2023, 06:57 by dev@lynne.ee: > > > >> Oct 29, 2023, 05:51 by michael@niedermayer.cc: > >> > >>> On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote: > >>> > >>>> Oct 28, 2023, 18:49 by michael@niedermayer.cc: > >>>> > >>>> > On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote: > >>>> > > >>>> >> It's been a while since we've had a release, and we've had > >>>> >> a lot of new features in. > >>>> >> We did say we would make releases more often, and I think > >>>> >> it's about time we have a new release. > >>>> >> > >>>> >> Anything anyone wants to have merged or should we branch > >>>> >> off 6.1 in a few days? > >>>> >> > >>>> > > >>>> > Whats the status of this ? > >>>> > I can branch 6.1 anytime > >>>> > > >>>> > It was just that jb told me > >>>> > "6.1 opportunity is gone. > >>>> > We're too late on the schedule, and noone had time to work on it,= so it is wiser to target 7.0 in January" > >>>> > > >>>> > but now i see on IRC > >>>> > make a damn release already > >>>> > j-b: drop MiNi from release maintership and nomina= te Lynne > >>>> > I pledge to bring back /slap IRC messages to those who fai= l to push the patches they want for release! > >>>> > durandal_1707: good point, we should look at doing another 5= =2E1.x release and a 6.0.x release. > >>>> > > >>>> > noone mentioned 5.1.x and 6.0.x to me before > >>>> > > >>>> > anyway, ill try to make releases from all maintained branches, > >>>> > > >>>> > and will branch 6.1 as soon as Lynne or others say everything is r= eady. > >>>> > > >>>> > thx > >>>> > > >>>> > >>>> It's never too late to make a release. If we do a release now, nothi= ng's stopping > >>>> us from doing a 7.0 and getting back on track with releases every tw= o months or so, > >>>> like the plan was. > >>>> > >>>> 7.0 is likely to be a pretty big release, with YUVJ removal, (xHE) A= AC+fixes, D3D12 hwdec, > >>>> Vulkan encode and Vulkan AV1, and VVC, and IAMF, and MLP work, so it= 's a good idea to > >>>> have a release before all this lands. > >>>> > >>>> I think the tree is in a pretty good state ATM, you should go ahead = and branch if you're > >>>> comfortable with it as well. > >>>> > >>> > >>> branch made > >>> > >> > >> Thanks. I'll get a blog post ready for the transform work, as kierank = wanted to post something, > >> and if users can know to who to point fingers to in case it degrades p= erformance on RPI1 devices. > >> > >> > >>>> Let's aim for a release by Sunday next week. That should give everyo= ne enough time to > >>>> backport fixes they want in. > >>>> > >>> > >>> I would aim for 1-3 weeks (when code and developers are ready) > >>> dont want to aim for a specific day, better pick a day when everythin= g is fine > >>> not too many distractions, ... > >>> > >>> Or is there something that favors us to be before a specific date ? > >>> > >> > >> Not really a reason, Sunday is just an optimistic date to aim for. > >> If there are no big fixes to backport to the branch, I think we can ta= rget it. > >> > > > > The nlmeans_vulkan patch I just sent is the last patch I'd like to have= in 6.1. > > Does anyone else have any patches they would like in 6.1? > > >=20 > Pushed the 2 patches. >=20 > Michael, do you think you can tag the release late tonight? > No one has said anything yet. > I'll write release notes for the website by then as well. ill try to make the release tomorrow if i do it now before going to bed likely something will go wrong thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them. --stZPNisUZAOqxp9d Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZU2LlQAKCRBhHseHBAsP q1pdAKCNKg8abQKO8ZJgOlOdbpANOKKVqACeIepzp3DUhy8ptD4x97w2rVza0Ng= =4rSY -----END PGP SIGNATURE----- --stZPNisUZAOqxp9d-- --===============7591695063026325517== 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". --===============7591695063026325517==--