From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 6.0
Date: Tue, 21 Feb 2023 14:20:26 +0100
Message-ID: <595e8067-f5fd-4256-8d77-ba600b6c9cf6@app.fastmail.com> (raw)
In-Reply-To: <20230221113838.GN1949656@pb2>
On Tue, 21 Feb 2023, at 12:38, Michael Niedermayer wrote:
> On Fri, Feb 10, 2023 at 06:47:03PM +0100, Michael Niedermayer wrote:
>> Hi all
>>
>> i plan to branch off release/6.0 from master in the next days
>> If theres something blocking and i should wait, please reply here
>>
>> 6.0 release will be maybe 1 week after the branch point
>> once it has branched all important fixes should be backported of course
>
> What name shall 6.0 bear ?
Why don’t you select 3 or 4 names from the list
And we do a proper vote on vote.ffmpeg.org?
--
Jean-Baptiste Kempf - President
+33 672 704 734
_______________________________________________
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:[~2023-02-21 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 17:47 Michael Niedermayer
2023-02-10 18:50 ` Lynne
2023-02-15 23:14 ` Michael Niedermayer
2023-02-17 3:50 ` Lynne
2023-02-11 5:44 ` Anton Khirnov
2023-02-21 11:38 ` Michael Niedermayer
2023-02-21 11:49 ` Paul B Mahol
2023-02-21 12:12 ` Gijs Peskens
2023-02-21 12:31 ` Reto Kromer
2023-02-21 12:31 ` Kieran Kunhya
2023-02-21 12:48 ` RADSL
2023-02-22 17:51 ` Michael Niedermayer
2023-02-21 13:20 ` Jean-Baptiste Kempf [this message]
2023-02-21 15:58 ` Michael Niedermayer
2023-02-24 4:01 ` Gyan Doshi
2023-02-25 12:58 ` Michael Niedermayer
2023-02-24 15:56 ` Niklas Haas
2023-02-24 16:40 ` Brad Isbell
2023-02-26 16:45 ` Michael Niedermayer
2023-02-26 13:18 ` Michael Niedermayer
2023-02-27 1:32 ` Wang Bin
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=595e8067-f5fd-4256-8d77-ba600b6c9cf6@app.fastmail.com \
--to=jb@videolan.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