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 3A90C4B31A for ; Mon, 3 Jun 2024 21:37:16 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7B9BD68D6B3; Tue, 4 Jun 2024 00:37:13 +0300 (EEST) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 392B468D612 for ; Tue, 4 Jun 2024 00:37:07 +0300 (EEST) Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-57a30b3a6cbso392545a12.1 for ; Mon, 03 Jun 2024 14:37:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717450626; x=1718055426; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=4fnTKvSL/pm+QU6Mxs7fNzLG2F8+fRVQylnN4ueifzY=; b=hHoW/F1fu3RDjxrU+vqubmRFMQSxTZ9Sxu0PLfqO83EOnUUJEQI/uJLW1ifbm3n3jU MmCklnVNSdtAueJGzIOQ+RkPw5i48iTv5lM2g28OuTD8L6g0mzui3PR+8DQQgG7PC5lU Uji6mjtYo9QvcREgIva3Cwp14KiaNvVu2jKtcufkBRA/K8J17bWqo7Iz17egyXpshOIF voD9y/AyaK8uhgH8rqFy0O2RnIfGpYq3KC7MT9u+4/EgIRZArBsNz3SPqmJp1POAU2nb n+QSM/y4E8MnBYVr/IftGE5DNl5Txw8vsLMYqv/cw81EiZ65HcGO12GWlogZ8w+nJ4by JiWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717450626; x=1718055426; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4fnTKvSL/pm+QU6Mxs7fNzLG2F8+fRVQylnN4ueifzY=; b=OkGslHWFglT2Q5NxQgrFQ3Jnia5c/oJAbup/Eulv5LRN6A4b4g02lE1w+m9RLOwnvo 6bNPLgV+G66F4jDEUf0s6s37aUf+T90AlUytz4I3pJee8hHOuH+UXx2/0/Hd1zyEtzdi J1R5QkJHnHSY1xKmDpYdQl49wxHfpC3oZsE+eR12jlIiX74K0iBk09b1gW218vJy4eQ4 Phe/HhYONIdbAjlf3s/ktdZaQI2MlmSN9hJtaz98pB2RRoDOl8TcJtgmbnIHlAvQrl3K rRL305yPIJDwxF1uVRHAzK6Wb211vVBbEdSy4dcgh6ju69cIo9Qr4WNwbFsp6QRURFcT IoUw== X-Gm-Message-State: AOJu0YxdfFuvo5OOeY3qR76x1IpAEF2a1uzPeN1XFExoVGpNS78ZCXgR vRorXsogeoxHXm+8S1+ce1O7bW+hNYegSx0i2cscl3vR+OsQEYxnA7fnpugSUMmBDv0pYitejYG kFc+NUXPHJpduJU+MCbxxzTbYE4JCIQ== X-Google-Smtp-Source: AGHT+IG7PVa182+NRPTTc3VvbMUL2mwSJj/CcbHp1qFcvuZfyAuFmnVDrvWNTFQi4feUd4R2899gSbANVsEqM809l1Y= X-Received: by 2002:a50:8e15:0:b0:57a:19f5:76cd with SMTP id 4fb4d7f45d1cf-57a363fc3cemr7207239a12.19.1717450625831; Mon, 03 Jun 2024 14:37:05 -0700 (PDT) MIME-Version: 1.0 References: <20240123192241.GA6420@pb2> <20240302225538.GI6420@pb2> <20240302231928.GJ6420@pb2> <20240603213237.GC2821752@pb2> In-Reply-To: <20240603213237.GC2821752@pb2> From: Sean McGovern Date: Mon, 3 Jun 2024 17:36:54 -0400 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Mon, Jun 3, 2024, 17:32 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 < > michael@niedermayer.cc> > > > > 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 ? > > 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 > > And last but not least, someone needs to write down when .0 and .1 > releases should > be made so I dont forget it :) > > thx > > [...] > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Nations do behave wisely once they have exhausted all other alternatives. > -- Abba Eban > _______________________________________________ > 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". > There are so many downstreams that this is probably a fool's errand. -- Sean McGovern > _______________________________________________ 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".