From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id C409B48CD9
	for <ffmpegdev@gitmailbox.com>; Wed, 24 Jan 2024 12:45:50 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 5E8BA68D083;
	Wed, 24 Jan 2024 14:45:47 +0200 (EET)
Received: from haasn.dev (haasn.dev [78.46.187.166])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 62896680276
 for <ffmpeg-devel@ffmpeg.org>; Wed, 24 Jan 2024 14:45:40 +0200 (EET)
Received: from localhost (46-227-103-81.hsi.r-kom.net [46.227.103.81])
 by haasn.dev (Postfix) with ESMTPSA id 5A5484151A
 for <ffmpeg-devel@ffmpeg.org>; Wed, 24 Jan 2024 13:45:39 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=haasn.xyz; s=mail;
 t=1706100339; bh=BmdKp12Eewn7iYvZvqnp6+H7AjNhRN+UXmRwU6SYwiA=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=ggOGmfFm4ygyuZ12aFuaRD7/cJqZ+3cbUxeiXifKDE5zudNm83E/p4Q0AfyYhhE86
 rD59vWAB3WY887Zr7f5HbGDvCL+S3MIKCH+tQuVp1CIlbsZvjrBwwMxzvHe186kS3E
 18DsKsMRMUqq4gxKbGlvgoZsNopgI5MmVaY2/+KA=
Date: Wed, 24 Jan 2024 13:45:33 +0100
Message-ID: <20240124134533.GB24498@haasn.xyz>
From: Niklas Haas <ffmpeg@haasn.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
In-Reply-To: <20240123192241.GA6420@pb2>
References: <20240123192241.GA6420@pb2>
MIME-Version: 1.0
Content-Disposition: inline
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 <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/20240124134533.GB24498@haasn.xyz/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On Tue, 23 Jan 2024 20:22:41 +0100 Michael Niedermayer <michael@niedermayer.cc> wrote:
> 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

I'd like to discuss YUVJ deprecation/removal. To what extent do we need to put
an additional deprecation warning on these? libswscale already prints a warning
on every use, informing the user that they need to set metadata correctly.

Is it feasible to replace YUVJ pixfmts by #define for their non-YUV equivalent
analogs in 7.0? 7.1?
_______________________________________________
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".