From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 6.0
Date: Sun, 26 Feb 2023 17:45:54 +0100
Message-ID: <20230226164554.GE1949656@pb2> (raw)
In-Reply-To: <20230221113838.GN1949656@pb2>
[-- Attachment #1.1: Type: text/plain, Size: 1950 bytes --]
On Tue, Feb 21, 2023 at 12:38:38PM +0100, 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 ?
>
> ill pick what has the highest number of votes
>
> Here are some previously suggested names:
> Darwin, De broglie, Desitter, Galois, Gauss, Heaviside, Jacobi, Maxwell, Mellin, Perelman, Poincaré, Ramanujan, Sagan, Viterbi, Voltaire, Von Neumann
Vote results:
Carl: 1 (Paul)
Dijkstra: 1 (Reto)
Jemison: 1 (Kieran)
Katherine Johnson: 1 (Kieran)
Heavens: 1 (RADSL)
Von Neumann: 1+L (Niklas)
6.0: 1 (Brad)
Von Neumann is the only who has more than 1 vote, whatever positive
value one assigns to previous votes, its the winner.
"Carl" above lacks a previous one as IIRC it is only Paul voting for
"Carl" every time.
If people want to use a more complex voting system next time, then
the first question to awnser is how to select which names would become
candidates ? or we need a system that allows candidates to be added
by anyone or allow a rather large list.
I mean i can surely pick some from the suggestsions but then iam not sure
how that would be better than this ML based vote.
Also deciding on another vote system for the name should happen not
in the last week before 6.1 especially when people want that release
to happen on time
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
[-- 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".
next prev parent reply other threads:[~2023-02-26 16:46 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
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 [this message]
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=20230226164554.GE1949656@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