Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] 7.0 blocking issues
Date: Mon, 25 Mar 2024 03:30:51 +0100
Message-ID: <20240325023051.GL6420@pb2> (raw)
In-Reply-To: <39ef0fe8-3cea-45a5-9287-5d09429887f3@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]

On Sun, Mar 24, 2024 at 09:35:29PM -0300, James Almer wrote:
> On 3/24/2024 9:03 PM, Michael Niedermayer wrote:
> > Hi all
> > 
> > Should i wait till all issues marked as blocking 7.0 on trac are fixed
> > before branching ?
> > 
> > btw if you click on "VIEW TICKETS" theres a link "{16} Release Blocking Issues"
> > ATM there are 2 again after i run into a new regression
> 
> Ticket #10886 is a matter of setting frame durations in the setts filter. I
> think Nicolas Haas said he'd look at it.
> 
> In any case, should they really block the release? They are bugs where the
> fix can be easily backported for a point release.

ok, what about the HEIF issues ? do you want to look into them before
i make the branch ?

i still have a few security issues i want to go over but that can happen
after we make the branch (assuming ossfuzz didnt again put 20 unrelated
ones under the same ticket number)

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

It is what and why we do it that matters, not just one of them.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-03-25  2:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25  0:03 Michael Niedermayer
2024-03-25  0:35 ` James Almer
2024-03-25  2:30   ` Michael Niedermayer [this message]
2024-03-25  6:20 ` Jean-Baptiste Kempf
2024-03-25 13:50   ` Niklas Haas
2024-03-25 20:20     ` Lynne
2024-03-25 21:10       ` Michael Niedermayer
2024-03-25 21:18         ` Kieran Kunhya
2024-03-25 21:57           ` Michael Niedermayer
2024-03-25 21:29         ` James Almer

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=20240325023051.GL6420@pb2 \
    --to=michael@niedermayer.cc \
    --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