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 F37EE40FB2 for ; Sun, 2 Jan 2022 14:12:51 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5EB5468B153; Sun, 2 Jan 2022 16:12:49 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1BD7268B132 for ; Sun, 2 Jan 2022 16:12:43 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 4261424017C for ; Sun, 2 Jan 2022 15:12:42 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id JKqT_8Nb0aJb for ; Sun, 2 Jan 2022 15:12:41 +0100 (CET) Received: from lain.red.khirnov.net (lain.red.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.red.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 68A4C240179 for ; Sun, 2 Jan 2022 15:12:41 +0100 (CET) Received: by lain.red.khirnov.net (Postfix, from userid 1000) id 3496016008E; Sun, 2 Jan 2022 15:12:37 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <20211231194024.GJ2829255@pb2> References: <20211125171932.GC2829255@pb2> <20211213152557.GL2829255@pb2> <3238136b-1f43-49ae-b2d6-ce98b98e24f0@www.fastmail.com> <20211222140322.GC2829255@pb2> <123bc8cf-2486-26ec-8c80-51815ccef543@gmail.com> <51c690dc-3c74-4a24-b83c-5fb81b0f8daf@beta.fastmail.com> <20211227235514.GY2829255@pb2> <20211231165245.GI2829255@pb2> <20211231194024.GJ2829255@pb2> Mail-Followup-To: FFmpeg development discussions and patches Date: Sun, 02 Jan 2022 15:12:37 +0100 Message-ID: <164113275711.2375.2561092812450139105@lain.red.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 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: Quoting Michael Niedermayer (2021-12-31 20:40:24) > On Fri, Dec 31, 2021 at 10:45:46PM +0530, Gyan Doshi wrote: > > > > > > On 2021-12-31 10:22 pm, Michael Niedermayer wrote: > > > On Tue, Dec 28, 2021 at 12:55:14AM +0100, Michael Niedermayer wrote: > > > > On Wed, Dec 22, 2021 at 05:44:42PM +0100, Jean-Baptiste Kempf wrote: > > > > > On Wed, 22 Dec 2021, at 15:05, James Almer wrote: > > > > > > Is the December target to get into the feature freeze schedule from > > > > > > distros? > > > > > No, it was set by me, in order to get the distro freezes from January. > > > > > > > > > > We can miss the target a bit this year, and then make it better for 2022. > > > > as you seem to know the distro freeze shedules > > > > can you clarify "a bit" ? > > > > > > > > iam asking just in case the channel patch doesnt make it before > > > > so i know when its time to stop waiting for it > > > ok > > > when do people want me to make the branch ? > > > any preferrances ? > > > should i do it now or continue waiting? > > > > > > I saw on IRC some sugestions to make it at a past commit to keep some > > > code out > > > > It would be nice to have a public date set a few days into the future. > > yes, i intended to do that, unless people wanted a ASAP/NOW branch > > i guess 3rd january seems like a good choice > 1st and 2nd as being close to newyear probably would not be ideal so > 3rd seems the soonest good date > but we can push this out more if people want? or also do it earlier > of course that assumes nothing unexpected happens > (and something unexpected always happens...) 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? -- Anton Khirnov _______________________________________________ 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".