Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Next release and regressions
Date: Tue, 18 Jan 2022 14:17:36 +0100
Message-ID: <20220118131736.GX2829255@pb2> (raw)
In-Reply-To: <131a7b49-12e6-5bdb-6cee-2a8b76d11d20@passwd.hu>


[-- 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".

      reply	other threads:[~2022-01-18 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 22:39 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 [this message]

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=20220118131736.GX2829255@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