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 D903B44110 for ; Thu, 26 Jan 2023 22:49:48 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E8DF368BD86; Fri, 27 Jan 2023 00:49:45 +0200 (EET) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id D3ECA68BABF for ; Fri, 27 Jan 2023 00:49:39 +0200 (EET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id DDE343200975; Thu, 26 Jan 2023 17:49:35 -0500 (EST) Received: from imap49 ([10.202.2.99]) by compute1.internal (MEProxy); Thu, 26 Jan 2023 17:49:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1674773375; x=1674859775; bh=Qr/MUiEwwCcF9QE75m282NIDdBun tgLsBwt8i50BIj0=; b=lHDe82RqdQ+qXrFTVJA1dS81u6ntzHjm4eMmRwRNGK7I Ko8sB8MmzFGzr4gy1E0C/85OJK5grMrGzYhQMRch7At1z/SSjqE+/oZGBAitFrRV EJdX94s0ex9h6f0sLQo2GFVg9NopUKlRDRJ0M+td33v4Fsveby7l5iN85EE94kad bDLM6F+Q5h62voxBFImXSko2393Nq2p7m5AQXEO/O6TneZixHXioSegFbcFwpLTW d4IB2SOZrZ8wW28r3lAF/TsSfHGI5alLodqrT/XloEB8qnfr9O7qBQd3g0NuOdY2 1NaF4lcKFSzC7P+MPfuinPPlKPrMPLHPjFHKyBeK+A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvhedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdflvggr nhdquegrphhtihhsthgvucfmvghmphhffdcuoehjsgesvhhiuggvohhlrghnrdhorhhgqe enucggtffrrghtthgvrhhnpeeiiefgvdffteekkeffvdeiffeijeethfevteeutdegvdeg feekgfektdelheefgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehjsgesvhhiuggvohhlrghnrdhorhhg X-ME-Proxy: Feedback-ID: i06904239:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id D180915A008E; Thu, 26 Jan 2023 17:49:34 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-85-gd6d859e0cf-fm-20230116.001-gd6d859e0 Mime-Version: 1.0 Message-Id: In-Reply-To: <20230126221614.GD1949656@pb2> References: <20230116133840.512-1-jamrial@gmail.com> <167457514256.4503.7425182589774123747@lain.khirnov.net> <6b01240d-95e2-db84-c40b-329a72b958c5@gmail.com> <7debdfb5-bbb3-e4c6-f95-a89a463d3abd@passwd.hu> <4997c7ce-3db3-4062-b3b4-f65719debc43@betaapp.fastmail.com> <4ee57c81-5811-4590-84f9-518104d1ce48@betaapp.fastmail.com> <20230126221614.GD1949656@pb2> Date: Thu, 26 Jan 2023 23:49:14 +0100 From: "Jean-Baptiste Kempf" To: "Michael Niedermayer" , ffmpeg-devel Subject: Re: [FFmpeg-devel] [PATCH 00/26] Major library version bump 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 Thu, 26 Jan 2023, at 23:16, Michael Niedermayer wrote: > I think in general these are the constraints to optimize our release timing > against: > > 1. We seem to want 2 releases per year Yes. > 2. If we do a major bump, it should ideally happen after a release not > before to give time for stabilization and to give max features to the old > API/ABI We said that one of those release would break ABI and API, and that would be the one at the dec/jan time > 3. The releases which get into distros should be LTS Yes > 4. LTS releases should be timed so that they are getting into major > distros > 5. What gets into major distros should have maximum features and > maximum stability > 6. We should try to stick to what we said previously > 7. We should have a predictable release cycle > So what do people think ? > when should i branch 5.2, when 6.0 ? and when 6.1 and then 6.2 or 7.0 when ? > also which should be LTS ? We've had this discussion the last time, notably for whether we should make 5.0 an LTS or 5.1 an LTS and we said: 5.0 in jan 2022, 5.1 in July 2022 with LTS 6.0 in jan 2023, 6.1 in July 2023 7.0 in jan 2024, 7.1 in July 2023 with LTS We said 5.0, 6.0 and 7.0 would be allowed to break API/ABI, aka big-bumps. We said we could do more 5.x or 6.x releases, if we needed more than 2 releases per year. We discussed that at several developer meetings, including the last one we had, a few weeks ago. > Btw, did we say that we will bump API/ABI in 6.0 or just that we will make > 6.0 in dec/jan ? Both. > Iam pretty bad at remembering these plans, my notes say 6.0 in dec 2022 but > that was not done because it would have competed with the LTS for inclusion > in distros No, because distro take a LONG time to integrate releases, because of the software dependencies adaptations. So, in Feb, they will use the last release of the previous major branch (here, a 5.1). Tbh, I don't see why we should do a 5.2, seeing that 6.0 would be the same features-set with just the ABI change, aka removing deprecated symbols. Also, doing a 5.2 which would not be a LTS, while 5.1 is a LTS is not only very weird, but it also goes against what we said last time, that the last of the 5.x would be LTS (similar for 7.1). I would just merge the bump, then branch 6.0 branch and wait a few weeks before releasing 6.0. If some people strongly want a 5.2, branch 5.2 before the bump and do a release at the same time. -- 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".