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 D553540FBF for ; Sun, 2 Jan 2022 14:51:06 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5BA6168B153; Sun, 2 Jan 2022 16:51:04 +0200 (EET) Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0DAF36807A1 for ; Sun, 2 Jan 2022 16:50:58 +0200 (EET) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zanevaniperen.com; s=key1; t=1641135057; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/FPUV3dJROOdvzCjPKBbUH71sDrcwUFtGU3gVoXR80Y=; b=dfUCaM2RxGbr2IVOQ4rLDLznOgTc3pRnUg8RGveb1zVdrNp8Uui95BF35fXnO/Mf0RceDL YXQ7exPGGhO70dGxnJq6j+EE0xPCePy7MXLB+iOjM29OxonpdRXFJKauHiwGmwmPVbFaXl tReXxU6rk5tEsd6i0UtXIw9wPfSt1wTpZMi9WrCgsZEpWKNLjlddiB3olhAC++kfLkrztz QK52M1QVpQR2zRr07pYvyg6FSHo0iYBIX9iiGPMVCqZ+CRUPLv7Kx7tnAj2nFNuUSL6Qf7 aJRBuhgD78Fti7U6IxeF74wueF+P7mwJo8302BT8BNb9XMp9paXSYk8XzB4v9w== From: Zane van Iperen To: ffmpeg-devel@ffmpeg.org Date: Mon, 03 Jan 2022 00:50:54 +1000 Message-ID: <35404072.zGk2CCufKt@morningstar> In-Reply-To: References: <20211125171932.GC2829255@pb2> <164113275711.2375.2561092812450139105@lain.red.khirnov.net> MIME-Version: 1.0 X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: zanevaniperen.com Subject: Re: [FFmpeg-devel] 5.0 release 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 Monday, 3 January 2022 12:29:02 AM AEST James Almer wrote: > > There were some disagreements on IRC a few days ago about what should > > and should not go into the release because of insufficient fuzzing and > > the danger of introducing security issues. > > > > To avoid conflicts around this in the future, I'd suggest (for future > > releases) to create the release branch a significant time (e.g. a month) > > before doing the actual release. > > > > Opinions? > > It's a good idea, but we need to be strict about it. As in, we need to > state that the moment the branch is made it's a definite feature freeze, > and only fixes, documentation changes and similar may be cherry-picked > into it (meaning nothing that usually comes with a version bump, even if > micro), much like we do for a point release, even if the initial release > was not tagged yet. > I completely agree, this is a *very* good idea. If people treat it like an existing release branch, i.e. only bugfixes, etc., then it would save this from happening again. Also means there wouldn't need to be a "don't add big things" announcement _somewhere_ on the ML. > Reverting something in the release branch is already going to be dirty > no matter what, because we do a minor bump to ensure the release has its > own soname. Right now that'd mean 5.0 will be lavf 59.13, while lacking > a demuxer available in lavf 59.12 Depends on what you mean by "lacking a demuxer"... One (hacky) option would be to replace it with a stub implementation that always fails. Or we could just branch off at 7cee3b3718 and cherry-pick anything we need back. There's only like four commits that need it (so far): 2f6360ff21, 9cfc7a2440, c417616762, and d6b2357edd. _______________________________________________ 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".