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 EA81E48CE7 for ; Wed, 24 Jan 2024 13:36:31 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5E8E868D093; Wed, 24 Jan 2024 15:36:28 +0200 (EET) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 3C35468CF84 for ; Wed, 24 Jan 2024 15:36:22 +0200 (EET) Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id CD9941060351 for ; Wed, 24 Jan 2024 13:36:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1706103381; s=s1; d=lynne.ee; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=TXEKX/8/SjrbZjRljJWoeejDufx4hpGwFjmwvUzZBgU=; b=1NS26C5DBXs5Y3zt4RM61CvxoXJ463yfU4VcaQoTXDpnJwhVq7euY78rg+spULga +WrM/RO2Nk1dJhMPNK0v40mRkQXT9jPRdIYHJYxtQKmx8WB2ZzKIoTZGzAYWO2XUqRb t7cTE21rY4VmbYjr92dwEwUn3G+xgnfL+HR5V8+pXlxwRlRnmS5QX+UdEmDTjKKcsFJ a58e4qVdr9yqQM94WE+CrbNzGAsC7F4uFGmlU/lpGuR/GteK8/hnTLcqDa/N47aIfSD mKoOD4VaRIZDoRvCmJbvwkBfrw84PjhikzVs4VOJLoNFraMvCLyY/pHB1zesLT5q2YO jKZQAreDxA== Date: Wed, 24 Jan 2024 14:36:21 +0100 (CET) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <170610264180.8914.16842399623818040125@lain.khirnov.net> References: <20240123192241.GA6420@pb2> <170608203677.8914.17390927215888357027@lain.khirnov.net> <170609942462.8914.4999646284365744972@lain.khirnov.net> <170610264180.8914.16842399623818040125@lain.khirnov.net> MIME-Version: 1.0 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: Jan 24, 2024, 14:24 by anton@khirnov.net: > Quoting Lynne (2024-01-24 14:14:00) > >> Jan 24, 2024, 13:30 by anton@khirnov.net: >> >> I have started on everything, and two things are finished but need polish, >> >> one is difficult and needs debugging while the other is more difficult. >> >> >> >> And with that release rate attitude, how do you think we can go to our one >> >> release every few months promise? >> >> >> > >> > I don't understand what you mean by this. >> > >> >> You mentioned half a year, but we planned to make a release every >> two months under the new release model from 2 years ago. >> > > I am not aware of such plans, and this sounds unfeasible to me. We > can barely follow the twice-per-year schedule. > https://ffmpeg.org//index.html#news > February 28th, 2023, FFmpeg 6.0 "Von Neumann"> Another release-specific change is that deprecated APIs will be removed after 3 releases, upon the > next major bump. This means that releases will be done more often and will be more organized. It's in the original proposal from 2 years ago. Releases will be much easier if we just do releases more often. _______________________________________________ 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".