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 147054A2A0 for ; Mon, 25 Mar 2024 21:57:18 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 0731568D5C6; Mon, 25 Mar 2024 23:57:17 +0200 (EET) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 5D63368D3B8 for ; Mon, 25 Mar 2024 23:57:10 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 96516E0004 for ; Mon, 25 Mar 2024 21:57:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1711403829; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=sb4qM1cBzixktIvK7mfZmQ1J+rK35PZ2oHOJoALDzhc=; b=jUPXQ+Mke5XbNq1aetgC3PbJQBfPE2y6XzrlkWQ7J3ZYJOtaRSMke2EsYYjvpmxhemKkWX Uwc4GICj0/GPwiWXHVlps6+yp7H9uY0AVK5nm1rXQ2q7RhESX0tffF2rSaAEW8UVm9VktZ BsSDVXBKmlVDsRWOD8fk6BsuqVHTBxxSNGOSaKp046yLJbPcvFEg9btsFp6wkxc3GiCxuD 8/ktKsR/ux6yw+wWRgL4v1xA0F0hxN6umNmaYd4cMrf9mw/wtk10v5vMolNUl49HRPXWcD YyPqTWrlMKYuzWQvWakfECu0Cv92Q28i0H6S5N27FaFYK+z0FceBA36CXfNMzw== Date: Mon, 25 Mar 2024 22:57:08 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240325215708.GT6420@pb2> References: <20240325000348.GJ6420@pb2> <2366ae95-3ea6-4c61-addc-b4a4667febb0@betaapp.fastmail.com> <20240325145019.GB17553@haasn.xyz> <20240325211040.GR6420@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC] 7.0 blocking issues 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="===============5431867511039826285==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5431867511039826285== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="YsxrXZYIR+8SWgAe" Content-Disposition: inline --YsxrXZYIR+8SWgAe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2024 at 09:18:09PM +0000, Kieran Kunhya wrote: > On Mon, 25 Mar 2024 at 21:10, Michael Niedermayer > wrote: >=20 > > On Mon, Mar 25, 2024 at 09:20:25PM +0100, Lynne wrote: > > > Mar 25, 2024, 14:50 by ffmpeg@haasn.xyz: > > > > > > > On Mon, 25 Mar 2024 07:20:56 +0100 "Jean-Baptiste Kempf" < > > jb@videolan.org> wrote: > > > > > > > >> Hello, > > > >> > > > >> On Mon, 25 Mar 2024, at 01:03, Michael Niedermayer wrote: > > > >> > Should i wait till all issues marked as blocking 7.0 on trac are > > fixed > > > >> > before branching ? > > > >> > > > >> I think you should branch now. > > > >> And get things fixed in the 7.0 branch. > > > >> > > > > > > > > +1 > > > > > > > > This is a big change and some breakage is inevitable. Most bugs will > > > > probably only be found once the software is released and deployed. > > > > > > > > When a big milestone gets bogged down by months (if not years) of > > > > "blocking bugs", my understanding is that it will simply never get > > > > released, and users might as well resort to using git master / nigh= tly > > > > builds at that point. > > > > > > > > (Any possible allusion to *other* big open source software projects= is > > > > purely coincidental) > > > > > > > > > > +1, we should branch so we can unblock master from receiving > > > > ok, ill make the branch within the next 24h probably > > > > We do have several open security issues still though (some have patches= on > > the ML) > > > > I still have to check if ossfuzz is hiding any issues in unrelated tick= ets > > (ossfuzz did that often previously and this can unveil surprises) > > > > Also iam behind with backporting security fixes to release branches, > > (this may seem unrelated but it isnt because i always try to backport > > each of my security fixes to all branches we still maintain at the same > > time, > > so id like to get the other branches uptodate with backports to keep > > backports > > in sync with a new 7.0) > > >=20 > Have you considered making a particular release an LTS so you don't have = to > backport to so many branches? The work is proportional to the number of patches in master to backport and approximately proportional to the amount of conflicts in the oldest bra= nch OTOH adding 5 more release branches between existing ones doesnt make a big difference, because if the patch conflicts nowhere theres nothing extra to = do and if it does conflict in one branch whatever needs to be done i do once not twice if a 2nd branch has the same reason for a conflict. fewer branches would just reduce the work on the tarball making and testing= side. So while marking releases "LTS" is not a bad idea. It wouldnt reduce the ba= ckporting work by a noticable amount i think thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell --YsxrXZYIR+8SWgAe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZgHzLgAKCRBhHseHBAsP q7o5AJ90U2rGjmADrk9qX/ikGHVG3pZMGwCcDJPswiCD1uqOStDxjUena3HOlIs= =5yhI -----END PGP SIGNATURE----- --YsxrXZYIR+8SWgAe-- --===============5431867511039826285== 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". --===============5431867511039826285==--