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 BADF348A20 for ; Wed, 24 Jan 2024 12:08:00 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C609A68D0D2; Wed, 24 Jan 2024 14:07:58 +0200 (EET) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B92A468CD0C for ; Wed, 24 Jan 2024 14:07:52 +0200 (EET) Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id 6D91B1060314 for ; Wed, 24 Jan 2024 12:07:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1706098071; 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=e4d/VBVvKYkBXg7E+1epFJSN1LN9A1RamyPzusUwUiA=; b=k1C3L+J0Zo76ER7ViwZiM5IpYCWwBSOP5RAVYKCnLXSnHopXj5a+l8dSIOA5EkPq MlCwGWvmBVSLB7A4/R73mv9ubg+o6llTwKXFvG/3TMoilfvxidMkyfjwQ9/V3X/KzYc Yks6SdouajmHjUtKacCbb4H7x3rRBNBhm7wwkOVg4OuQZH0ERmkFwq9dIGQOExAG1i7 mmtCobjcmfoaX1Uv+6b21vf3nvuhvCTCqL+SqyOE6aJpfAdAbjmaYktjtQL50QYjp2Q SVZrUWTnQg6grtKfVZiI9zxiYprj6J1i5Lr29cPfSxl93905ugNlbwW9KEp09wHcDwc jNBxLwIPsQ== Date: Wed, 24 Jan 2024 13:07:51 +0100 (CET) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <170608203677.8914.17390927215888357027@lain.khirnov.net> References: <20240123192241.GA6420@pb2> <170608203677.8914.17390927215888357027@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, 08:40 by anton@khirnov.net: > Quoting Lynne (2024-01-23 21:18:29) > >> Jan 23, 2024, 20:22 by michael@niedermayer.cc: >> >> > Hi all >> > >> > As it was a little difficult for me to not loose track of what is >> > blocking a release. I suggest that for all release blocking issues >> > open a ticket and set Blocking to 7.0 >> > that way this: >> > https://trac.ffmpeg.org/query?blocking=~7.0 >> > >> > or for the ones not closed: >> > https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&blocking=~7.0 >> > >> > will list all blocking issues >> > >> > Ive added one, for testing that, i intend to add more if i see something >> > >> > What is blocking? (IMHO) >> > * regressions (unless its non possible to fix before release) >> > * crashes >> > * security issues >> > * data loss >> > * privacy issues >> > * anything the commuity agrees should be in the release >> > >> >> On my side, what I want: >> Vulkan AV1. It's ready to be posted once the spec goes public very very soon. >> This shouldn't even become a blocker unless you want a release tagged immediately. >> >> And those that I don't consider as blockers, just something nice to have: >> >> Vulkan encode (H264). Needs about a week of work. >> HE-AAC 960-point. >> Preliminary xHE-AAC support. Not sure. >> AAC prepad fixes - perhaps partial (off by one sample for SBR). >> > > Sigh. We already had this drama last time, must we do it again? > If you haven't even started working on it yet, then it shouldn't be a > blocker for the release, it can wait half a year for 7.1. > Which part of "don't consider as blockers" did you find difficult to understand? I even added newlines top and bottom for you to laser onto that sentence. 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? _______________________________________________ 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".