From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] 7.0 blocking issues
Date: Sun, 24 Mar 2024 21:35:29 -0300
Message-ID: <39ef0fe8-3cea-45a5-9287-5d09429887f3@gmail.com> (raw)
In-Reply-To: <20240325000348.GJ6420@pb2>
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.
>
> thx
>
>
> _______________________________________________
> 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".
_______________________________________________
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".
next prev parent reply other threads:[~2024-03-25 0:35 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 [this message]
2024-03-25 2:30 ` Michael Niedermayer
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=39ef0fe8-3cea-45a5-9287-5d09429887f3@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