Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] 7.0 release
Date: Thu, 4 Apr 2024 08:50:12 -0300
Message-ID: <d4fbcd63-e4bb-4d2c-92c6-0c0576a80006@gmail.com> (raw)
In-Reply-To: <20240404114715.GV6420@pb2>

On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
> On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
>> Quoting Michael Niedermayer (2024-04-04 00:57:39)
>>> Hi
>>>
>>> I will try to make the 7.0 release from the release branch in the next 48h
>>> (with some luck but easy possible it will get delayed)
>>> i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
>>
>> IMO people are overly eager to mark everything as 'blocking'.
> 
> No, thats not true, very few bugs are marked as blocking, we have 2837
> open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
> blocking maximum at any time over the last weeks

The bug marked as blocking has no available sample, and the commit you 
say generated the regression just moved a failure path around, so how 
can it change the reported aspect ratio of the input?
_______________________________________________
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".

  reply	other threads:[~2024-04-04 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 22:57 Michael Niedermayer
2024-04-04  5:27 ` Jean-Baptiste Kempf
2024-04-04  7:12 ` Anton Khirnov
2024-04-04 11:47   ` Michael Niedermayer
2024-04-04 11:50     ` James Almer [this message]
2024-04-04 12:29       ` Michael Niedermayer
2024-04-04 12:51         ` James Almer
2024-04-04 16:39           ` Michael Niedermayer
2024-04-04 12:46       ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4fbcd63-e4bb-4d2c-92c6-0c0576a80006@gmail.com \
    --to=jamrial@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git