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 70D834B31D for ; Mon, 3 Jun 2024 21:41:11 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 229F468D687; Tue, 4 Jun 2024 00:41:09 +0300 (EEST) Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BC6BE68D470 for ; Tue, 4 Jun 2024 00:41:01 +0300 (EEST) Received: by mail-pj1-f47.google.com with SMTP id 98e67ed59e1d1-2c1b9152848so3279966a91.1 for ; Mon, 03 Jun 2024 14:41:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717450859; x=1718055659; darn=ffmpeg.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=Kasa345C2jAEr0P8/+n5RpAaSx7rMZdL06l8wG59tkQ=; b=SCO7/lTJiXTp32vlzDHmQzJQGml2x7BFyeApNA0kjuv86qsVGccquvTIyWn7eouIx2 1k1Ln0Et48kOKwH/R3yYfkaEd6b/XsD0Cz79tZcRVnTApakmJCuNe6Eg1QKIY+biY8wy 4PO5BOnnPp2vqUw8G+j3OaXpHwOreQ3y8U1K2bIg5z3lzn2iDt6kW1IGwuN5m+efhsXM 67sGkkjyIq2CWJwdBCF2rBrPGdMG16tq99Mq+Hs47P5hhqsqY70x1cS5H5Tt67oPQVlq HGkgDKC9CwAlQs2w3L23a1v45AxtnixNncJxywJxwjnKTq2hiM1BrPspsZ4wbyVRRK67 55PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717450859; x=1718055659; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Kasa345C2jAEr0P8/+n5RpAaSx7rMZdL06l8wG59tkQ=; b=iIRhC/7kZfejSMenR1CuA6gc1ywEzkVH/PZMHjpfYWReELjbB2ll+LbEgtrJdN/71X +3xaqp/MDdhwU+7qzyi+1UWPhsGm2eeEjZPMaLPOQUReciSB8iT3N5DZ6pDrp5HP5ZnX LoBghwgaEgIFDkfEiDtrgqEXwkBmNX6vBCSyoVZUCfSPDnrJVhOHupBK2xQvrlraqg26 sXG6FJViI5Zei/lnqfqcLZQ+Qdl8c1nLUvHQoEjFCF/OM55IfWjMRvmYcJlnKGhUmwO8 HwP/sJfbR8w4mS2GiAEPvGmLak8gyZsXnBar0hcyNWcEyy/vigKWHPdUt4h1e4xFHpoZ TYLA== X-Gm-Message-State: AOJu0YxEsQUp1rF7qn4Vwx6kMlc0VRYdW3U35Fo9uOZ9n5Y/wDkiaZyF RkPz/WE6mjhZYyBtabvT0GriJ0+Uw0qtXeXp098XGD/3gsr0PWQJSpOMWg== X-Google-Smtp-Source: AGHT+IEVm3dKYCyEZpRygtadaJd/MBrwKYRUcHOgsr3a/3BnDO15wHEa3Yn8dLc3EjLScIEYPMyxrw== X-Received: by 2002:a17:90a:c284:b0:2c1:b88a:3a22 with SMTP id 98e67ed59e1d1-2c1dc5cd779mr8112386a91.45.1717450858608; Mon, 03 Jun 2024 14:40:58 -0700 (PDT) Received: from [192.168.0.16] ([190.194.167.233]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2c1c27ad277sm7134378a91.6.2024.06.03.14.40.57 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Jun 2024 14:40:58 -0700 (PDT) Message-ID: <4f35870d-3c4f-4ee7-8a83-c337490e8ca7@gmail.com> Date: Mon, 3 Jun 2024 18:41:03 -0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: ffmpeg-devel@ffmpeg.org References: <20240123192241.GA6420@pb2> <20240302225538.GI6420@pb2> <20240302231928.GJ6420@pb2> <20240603213237.GC2821752@pb2> Content-Language: en-US From: James Almer In-Reply-To: <20240603213237.GC2821752@pb2> Subject: Re: [FFmpeg-devel] FFmpeg 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 6/3/2024 6:32 PM, Michael Niedermayer wrote: > On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote: >> On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote: >>> On 2024-03-02 20:39:08 -0500, Sean McGovern wrote: >>>> On Sat, Mar 2, 2024, 18:19 Michael Niedermayer >>>> wrote: >>>> >>>>> On Sun, Mar 03, 2024 at 12:06:14AM +0100, Sebastian Ramacher wrote: >>>>>> On 2024-03-02 23:55:38 +0100, Michael Niedermayer wrote: >>>>>>> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote: >>>>>>>> Hi all >>>>>>>> >>>>>>>> As it was a little difficult for me to not loose track of what is >>>>>>>> blocking a release. I suggest that for all release blocking issues >>>>>>>> open a ticket and set Blocking to 7.0 >>>>>>>> that way this: >>>>>>>> https://trac.ffmpeg.org/query?blocking=~7.0 >>>>>>>> >>>>>>>> or for the ones not closed: >>>>>>>> >>>>> https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&blocking=~7.0 >>>>>>>> >>>>>>>> will list all blocking issues >>>>>>>> >>>>>>>> Ive added one, for testing that, i intend to add more if i see >>>>> something >>>>>>>> >>>>>>>> What is blocking? (IMHO) >>>>>>>> * regressions (unless its non possible to fix before release) >>>>>>>> * crashes >>>>>>>> * security issues >>>>>>>> * data loss >>>>>>>> * privacy issues >>>>>>>> * anything the commuity agrees should be in the release >>>>>>> >>>>>>> We still have 3 blocking issues on trac >>>>>>> >>>>>>> do people want me to wait or ignore them and branch ? >>>>>>> Iam not sure when the exact deadline is but if we keep waiting >>>>>>> we will not get into ubuntu 24.04 LTS >>>>>> >>>>>> 24.04 is past feature freeze, so it's too late for that. >>>>> >>>>> we should aim earlier in the future then. >>>>> >>>>> >>>> >>>> LTS is only every 2 years, yes? >>> >>> Yes >>> >>>> How do we make sure this doesn't happen in 2026? How much of a gap is there >>>> between feature freeze and release? >>> >>> Not involved in Ubuntu, so that's from past experience: feature >>> freeze is usually about two months before the release. >>> >>> So here's the catch: Debian's timeline also needs to be taken into >>> account. If the ffmpeg release does not involve the removal of deprecated API and >>> a SONAME bump, then the time from ffmpeg to release to upload to Debian >>> unstable and then import in Ubuntu is short. In this case, I am sure >>> that I could convince Ubuntu maintainers to import it even during >>> feature freeze. >>> >>> But with SONAME bumps and changes in the API, it takes a lot more time >>> to work through the high number of ffmpeg reverse dependencies. In that >>> case, plan a release at least 6 months before an Ubuntu LTS release. >> >> >> >>> >>> We usually have to rely on upstream maintainers to adopt to the >>> changes and that take times. Many moons ago Anton helped with providing >>> patches, but for the last couple of API changes it took some months from >>> "dear maintainer, here is ffmpeg X for testing, please fix the build of >>> your package" to actually doing all uploads and rebuilds. For example, >>> the transition to ffmpeg 6.0 was started in July 2023 and was done in >>> December 2023. >> >> Just as a FYI: ffmpeg 7.0 breaks close to 70 reverse dependencies in >> Debian. The list is available at [1]. So if you want ffmpeg X to be in >> Debian Y or Ubuntu Z, X needs to be released at least half a year before >> Y or Z freeze. > > Is there something that ffmpeg can do to reduce this breakage ? > (i know its a bit of a lame question as its API brekages but i mean > can the policy we have about deprecating API/ABI be amended in some way > to make this easier ? Well, no. Breakages are expected when you remove API. The real question is why so many projects wait until the old API is gone to migrate. What we removed in 7.0 has had its replacement in place for a couple years, since 5.1. > > Also am i correct that it should be easier if a X.1 with same API/ABI that is > released 6 month after X.0 is targetet for the release ? Thats in fact kind > of what i would have preferred anyway as the .1 likely has also fewer bugs IMO yes, it would be best if we aim at having distros shipping X.1 or higher rather than the first version after a major bump. Debian stable currently ships 5.1, for example. > > And last but not least, someone needs to write down when .0 and .1 releases should > be made so I dont forget it :) > > thx > > [...] > > > _______________________________________________ > 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". _______________________________________________ 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".