] 5.0 blocking issues
On Wed, Jan 12, 2022 at 07:37:03AM +0100, Lynne wrote:
8 Jan 2022, 17:30 by mich...@niedermayer.cc:
Hi all
This is a simple go/no go call
if you know of something that still should go into 5.0 please reply here
with a list of what you are working on and a timelimit until
On Wed, 2022-01-12 at 21:35 +, Soft Works wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of Michael
> > Niedermayer
> > Sent: Wednesday, January 12, 2022 5:31 PM
> > To: FFmpeg development discussions and patches
> > Subject: Re
On Wed, Jan 12, 2022 at 01:41:18PM -0300, James Almer wrote:
>
>
> On 1/12/2022 1:36 PM, Nicolas George wrote:
> > Michael Niedermayer (12022-01-12):
> > > Iam really bad at keeping track of everything everyone asks to be
> > > included and then notice when it was included fully with nothing
> >
> -Original Message-
> From: ffmpeg-devel On Behalf Of Michael
> Niedermayer
> Sent: Wednesday, January 12, 2022 5:31 PM
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] 5.0 blocking issues
>
> On Wed, Jan 12, 2022 at 07:37:03AM +
Jean-Baptiste Kempf (12022-01-12):
> > I consider this a toxic configuration. FFmpeg does not "need" to be a
> > "serious" project, we just need free time to write beautiful and
> > efficient code.
>
> Are you _sure_ this is an opinion that is shared by the majority of
> contributors on this mail
On Wed, 12 Jan 2022, at 17:47, Nicolas George wrote:
> I consider this a toxic configuration. FFmpeg does not "need" to be a
> "serious" project, we just need free time to write beautiful and
> efficient code.
Are you _sure_ this is an opinion that is shared by the majority of
contributors on thi
James Almer (12022-01-12):
> I think it should be more like, as release manager, he decides when to cut a
> branch and when to tag a release within that branch, and in either case
> giving a warning with some time in advance.
> Saying "Anything else?" then waiting for people and constantly postponi
On 1/12/2022 1:36 PM, Nicolas George wrote:
Michael Niedermayer (12022-01-12):
Iam really bad at keeping track of everything everyone asks to be
included and then notice when it was included fully with nothing
missing and no amendmends.
Maybe we could put a RELEASE_BLOCKER file in release bra
Michael Niedermayer (12022-01-12):
> Iam really bad at keeping track of everything everyone asks to be
> included and then notice when it was included fully with nothing
> missing and no amendmends.
> Maybe we could put a RELEASE_BLOCKER file in release branches in the future
> and everyone can li
On Wed, Jan 12, 2022 at 07:37:03AM +0100, Lynne wrote:
> 8 Jan 2022, 17:30 by mich...@niedermayer.cc:
>
> > Hi all
> >
> > This is a simple go/no go call
> > if you know of something that still should go into 5.0 please reply here
> > with a list of what you are working on and a timelimit until wh
8 Jan 2022, 17:30 by mich...@niedermayer.cc:
> Hi all
>
> This is a simple go/no go call
> if you know of something that still should go into 5.0 please reply here
> with a list of what you are working on and a timelimit until when you
> will be done with it
>
> if you think everything is ready fo
Michael Niedermayer:
> Hi all
>
> This is a simple go/no go call
> if you know of something that still should go into 5.0 please reply here
> with a list of what you are working on and a timelimit until when you
> will be done with it
>
> if you think everything is ready for the release, then too
The first patch in my just-sent lavf set:
lavf/udp: do not return an uninitialized value from udp_open()
(message-id <20220110165143.2292-1-an...@khirnov.net>)
should go into 5.0 (and 4.4).
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffm
> > A regression issue: avformat/movenc: fix duration in mdhd box
> > https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_7d4d80dc34db3f53572f9d76e0ee5aee3...@qq.com/
>
> https://patchwork.ffmpeg.org/check/48152/
>
> Make fate failed?
> make: *** [fate-copy-trac3074] Error 1
> make: *** [f
On Mon, Jan 10, 2022 at 11:09:11AM +0800, "zhilizhao(赵志立)" wrote:
>
>
> > On Jan 9, 2022, at 12:30 AM, Michael Niedermayer
> > wrote:
> >
> > Hi all
> >
> > This is a simple go/no go call
> > if you know of something that still should go into 5.0 please reply here
> > with a list of what you
> On Jan 9, 2022, at 12:30 AM, Michael Niedermayer
> wrote:
>
> Hi all
>
> This is a simple go/no go call
> if you know of something that still should go into 5.0 please reply here
> with a list of what you are working on and a timelimit until when you
> will be done with it
A regression is
8 Jan 2022, 17:30 by mich...@niedermayer.cc:
> Hi all
>
> This is a simple go/no go call
> if you know of something that still should go into 5.0 please reply here
> with a list of what you are working on and a timelimit until when you
> will be done with it
>
> if you think everything is ready fo
> -Original Message-
> From: ffmpeg-devel On Behalf Of Michael
> Niedermayer
> Sent: Saturday, January 8, 2022 5:30 PM
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] 5.0 blocking issues
>
> Hi all
>
> This is a simple
Le sam. 8 janv. 2022 à 10:30, Michael Niedermayer
a écrit :
>
> Hi all
>
> This is a simple go/no go call
> if you know of something that still should go into 5.0 please reply here
> with a list of what you are working on and a timelimit until when you
> will be done with it
>
> if you think every
Hi all
This is a simple go/no go call
if you know of something that still should go into 5.0 please reply here
with a list of what you are working on and a timelimit until when you
will be done with it
if you think everything is ready for the release, then too feel free to
reply (assuming few oth
20 matches
Mail list logo
