* [FFmpeg-devel] [RFC] Next release and regressions
@ 2022-01-17 22:39 Michael Niedermayer
2022-01-17 22:46 ` Jean-Baptiste Kempf
2022-01-17 23:22 ` Marton Balint
0 siblings, 2 replies; 5+ messages in thread
From: Michael Niedermayer @ 2022-01-17 22:39 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 592 bytes --]
Hi
Trac lists 162 non closed bugs with keyword regression
https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&keywords=~regression
Our next major release maybe will be next december
I suggest we try to reduce the number of regression bugs, and also to
add fate tests for as many of these when they are fixed as easily
possible.
Thanks
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin
[-- 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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [RFC] Next release and regressions
2022-01-17 22:39 [FFmpeg-devel] [RFC] Next release and regressions Michael Niedermayer
@ 2022-01-17 22:46 ` Jean-Baptiste Kempf
2022-01-17 22:59 ` Michael Niedermayer
2022-01-17 23:22 ` Marton Balint
1 sibling, 1 reply; 5+ messages in thread
From: Jean-Baptiste Kempf @ 2022-01-17 22:46 UTC (permalink / raw)
To: Michael Niedermayer, FFmpeg development discussions and patches
Heya,
On Mon, 17 Jan 2022, at 23:39, Michael Niedermayer wrote:
> Trac lists 162 non closed bugs with keyword regression
> https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&keywords=~regression
>
> Our next major release maybe will be next december
When is 5.1.0 ? June/July?
If so, then reducing regressions would be very nice at that time.
jb
--
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [RFC] Next release and regressions
2022-01-17 22:46 ` Jean-Baptiste Kempf
@ 2022-01-17 22:59 ` Michael Niedermayer
0 siblings, 0 replies; 5+ messages in thread
From: Michael Niedermayer @ 2022-01-17 22:59 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 1127 bytes --]
On Mon, Jan 17, 2022 at 11:46:24PM +0100, Jean-Baptiste Kempf wrote:
> Heya,
>
> On Mon, 17 Jan 2022, at 23:39, Michael Niedermayer wrote:
> > Trac lists 162 non closed bugs with keyword regression
> > https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&keywords=~regression
> >
> > Our next major release maybe will be next december
>
> When is 5.1.0 ? June/July?
Sounds like that would fit
> If so, then reducing regressions would be very nice at that time.
I think regressions should always be a thing to fix, not just
at time of a release.
Doing it just at a release will make the whole more entangled
and then when there are 30 issues one wants to fix and time for
only fixing 10 the fixes will be worse and people would skip
writing fate tests as thats the easiest to skip when time is
short
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Let us carefully observe those good qualities wherein our enemies excel us
and endeavor to excel them, by avoiding what is faulty, and imitating what
is excellent in them. -- Plutarch
[-- 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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [RFC] Next release and regressions
2022-01-17 22:39 [FFmpeg-devel] [RFC] Next release and regressions Michael Niedermayer
2022-01-17 22:46 ` Jean-Baptiste Kempf
@ 2022-01-17 23:22 ` Marton Balint
2022-01-18 13:17 ` Michael Niedermayer
1 sibling, 1 reply; 5+ messages in thread
From: Marton Balint @ 2022-01-17 23:22 UTC (permalink / raw)
To: FFmpeg development discussions and patches
On Mon, 17 Jan 2022, Michael Niedermayer wrote:
> Hi
>
> Trac lists 162 non closed bugs with keyword regression
> https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&keywords=~regression
>
> Our next major release maybe will be next december
>
> I suggest we try to reduce the number of regression bugs, and also to
> add fate tests for as many of these when they are fixed as easily
> possible.
Regression fixes should be backported to stable branches, unless they are
very invasive. I'd rather suggest a bug hunt of all issues categorized as
important, mostly regressions, some crashes.
Regards,
Marton
_______________________________________________
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [RFC] Next release and regressions
2022-01-17 23:22 ` Marton Balint
@ 2022-01-18 13:17 ` Michael Niedermayer
0 siblings, 0 replies; 5+ messages in thread
From: Michael Niedermayer @ 2022-01-18 13:17 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 1114 bytes --]
On Tue, Jan 18, 2022 at 12:22:26AM +0100, Marton Balint wrote:
>
>
> On Mon, 17 Jan 2022, Michael Niedermayer wrote:
>
> > Hi
> >
> > Trac lists 162 non closed bugs with keyword regression
> > https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&keywords=~regression
> >
> > Our next major release maybe will be next december
> >
> > I suggest we try to reduce the number of regression bugs, and also to
> > add fate tests for as many of these when they are fixed as easily
> > possible.
>
> Regression fixes should be backported to stable branches, unless they are
yes
> very invasive. I'd rather suggest a bug hunt of all issues categorized as
> important, mostly regressions, some crashes.
i was slightly hesitating with suggesting "important" as i feared bikedsheding
over what is "important", "regression" is more clearly defined
but of course important bugs should be fixed
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No great genius has ever existed without some touch of madness. -- Aristotle
[-- 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".
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-01-18 13:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-17 22:39 [FFmpeg-devel] [RFC] Next release and regressions Michael Niedermayer
2022-01-17 22:46 ` Jean-Baptiste Kempf
2022-01-17 22:59 ` Michael Niedermayer
2022-01-17 23:22 ` Marton Balint
2022-01-18 13:17 ` Michael Niedermayer
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