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 03A1D47E6D for ; Sun, 29 Oct 2023 17:02:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5B9CA68CBE9; Sun, 29 Oct 2023 19:02:25 +0200 (EET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C3BF568CA63 for ; Sun, 29 Oct 2023 19:02:18 +0200 (EET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 20E823200368 for ; Sun, 29 Oct 2023 13:02:17 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute3.internal (MEProxy); Sun, 29 Oct 2023 13:02:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1698598936; x=1698685336; bh=h/silIOgZijAe /JrItd6HuvxbBaxHO9OkqDBuFWCaBE=; b=h0rSfCMFxcVGZjdQIi5gh9Vemz2Z8 gg99Y2WUSAZBXYyyqpV2ynBkIPuWrfAwHIN+SwvefHZWJ6AUItSdzH2N5SeUygpF 90eemMNEsAwqNA0YPRPYLS6SmNoEQ+oJ26gzHqp+q04ABPwAkoi1MPgqooNrbGoP vp6mFm8kRZ9D9bUN08bofcjqHYDdLbwrSJpF+An+//kPdWW5vLK63K8RS8y3a2w1 zE7UmvawFpAvQwU5/UzRK7fF7UXsflxLPbeTcGWygz2TlZvAONh8Ya3czBt25INn QwvwS+U5qDctpLAme6sEuhE3gPBW4o30rlQdMSFU8rF4pRS3qp6rteswQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrleekgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdflvggrnhdquegrphhtihhsthgvucfmvghmphhffdcuoehj sgesvhhiuggvohhlrghnrdhorhhgqeenucggtffrrghtthgvrhhnpeeiiefgvdffteekke ffvdeiffeijeethfevteeutdegvdegfeekgfektdelheefgfenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehjsgesvhhiuggvohhlrghnrdhorh hg X-ME-Proxy: Feedback-ID: i06904239:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id DF72815A0091; Sun, 29 Oct 2023 13:02:15 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1048-g9229b632c5-fm-20231019.001-g9229b632 MIME-Version: 1.0 Message-Id: In-Reply-To: <82c39d8d-c9d4-418d-8136-7ab349765123@gmail.com> References: <20231028164945.GC3543730@pb2> <82c39d8d-c9d4-418d-8136-7ab349765123@gmail.com> Date: Sun, 29 Oct 2023 18:01:55 +0100 From: "Jean-Baptiste Kempf" To: ffmpeg-devel 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: 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 Sun, 29 Oct 2023, at 17:49, James Almer wrote: > On 10/29/2023 1:42 PM, Jean-Baptiste Kempf wrote: >> Hello, >> >> On Sat, 28 Oct 2023, at 18:49, Michael Niedermayer wrote: >>> noone mentioned 5.1.x and 6.0.x to me before >> >> Our last releases from our two major bracnhes, are a 5.1.3 (which is a LTS branch) and a 6.0.0. >> >> Both of those have not had backports and releases of all the security issues, nor on the major regressions found (if any). >> >> Also, if they had some commits for security reasons, we should have a release at least every 90 days (3 months), because this is the standard for the security issues reporting (after that time, the security community makes them public). >> And seeing the number of fuzzing fixes, this is likely important. >> >> So, yes, I think having a 5.1.4 and 6.0.1 with the security fixes is of the utmost importance. >> >>> 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" >> >> Yes, we said we would make a new major version for January (which will slip in February, as usual :D). >> So, doing a 6.1.0 now, while 7.0 is not far away, might be a lot of work and it might not worth it. >> Notably since at the time of 7.0, there might be not enough new things to cut a release. >> >> So I'm not against a release for 6.1 at all, but I believe focusing on minor releases for security and on 7.0 with the next major deprecations is more important. >> If we can do all of those, and keep more or less the timing for 7.0, please be my guest for 6.1. > > Lynne made a list of the things that should (hopefully) make it to 7.0 > for early 2024 (E.g. YUVJ removal, D3D12 hwdec, Vulkan encode, VVC, > IAMF) plus Anton's CLI scheduler work, not to mention it will feature a > major version bump and all the deprecated API removal that brings. So > even with not a lot of things, the few it will get in these few months > will be pretty big and appealing. > > 6.1 doesn't need to be supported for too long, but it's a good release > to have as it will feature a year worth of development while being 6.0 > ABI compatible, for those distros that care. Excellent then. -- Jean-Baptiste Kempf - President +33 672 704 734 _______________________________________________ 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".