From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg 5.1
Date: Thu, 7 Jul 2022 22:51:00 +0200
Message-ID: <e82715f7-e811-b814-8d08-f80b00aa115a@rothenpieler.org> (raw)
In-Reply-To: <20220707204757.GV396728@pb2>
On 07.07.2022 22:47, Michael Niedermayer wrote:
> On Tue, Jun 07, 2022 at 01:35:00PM +0200, Michael Niedermayer wrote:
>> Hi all
>>
>> As was discussed previously the 5.1 release should be in june/july
>> That means in the next weeks probably!
>> If you know of any regressions, security issues or other major bugs,
>> please help fixing them
>>
>> Also as was suggested before, this release will get the "LTS" tag
>> unless people feel thats a bad idea of course
>
> i plan to branch 5.1 of master soon (in the next 3-7 days hopefully)
> and do the release ~7 days afterwards. This assumes no major issues pop
> up
> if theres anything you are working on that i should wait for, reply here
> and also (that one is important) tell me once you resolved the issue so i
> dont have to guess from git commits if an issue got fully resolved
>
> also 5.1 still needs a name i think
> previosuly suggested names i found in my very unorgnaized notes:
> Mellin, Gauss, Galois, Viterbi, Darwin, Von Neumann, lorentz, poincaré, desitter, de broglie
> feel free to add more
> feel free to vote for anything
>
> in case of a tie i will pick one of the tied winners
>
> thx
Would be cool to get ddagrab and the first GSoC filter in.
Both are on the ML and I plan to merge both in the next couple days, if
no issues pop up.
ddagrab depends on things like the lavfi.c changes, but it seems like
they are good to go now as well, so nothing should be a blocker.
_______________________________________________
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:[~2022-07-07 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:35 Michael Niedermayer
2022-06-09 18:13 ` Neal Gompa
2022-06-19 20:59 ` Marton Balint
2022-06-20 0:22 ` Neal Gompa
2022-07-07 22:52 ` Marton Balint
2022-07-07 20:47 ` Michael Niedermayer
2022-07-07 20:51 ` Timo Rothenpieler [this message]
2022-07-07 20:54 ` James Almer
2022-07-08 10:17 ` Timo Rothenpieler
2022-07-08 10:23 ` Timo Rothenpieler
2022-07-08 11:49 ` James Almer
2022-07-08 8:36 ` Jean-Baptiste Kempf
2022-07-08 8:52 ` Paul B Mahol
2022-07-08 13:52 ` Michael Niedermayer
2022-07-08 14:54 ` Leo Izen
2022-07-09 17:17 ` Andreas Rheinhardt
2022-07-21 17:09 ` 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=e82715f7-e811-b814-8d08-f80b00aa115a@rothenpieler.org \
--to=timo@rothenpieler.org \
--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