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] 7.0 release
Date: Thu, 4 Apr 2024 13:47:15 +0200
Message-ID: <20240404114715.GV6420@pb2> (raw)
In-Reply-To: <171221472457.28449.1148639475917988957@lain.khirnov.net>


[-- Attachment #1.1: Type: text/plain, Size: 2155 bytes --]

On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2024-04-04 00:57:39)
> > Hi
> > 
> > I will try to make the 7.0 release from the release branch in the next 48h
> > (with some luck but easy possible it will get delayed)
> > i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
> 
> IMO people are overly eager to mark everything as 'blocking'.

No, thats not true, very few bugs are marked as blocking, we have 2837
open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
blocking maximum at any time over the last weeks


> Not every
> bug ... should be blocking,

true


> and not every regression

IMO, every regression should by default be blocking. Adding regressions
is not ok. And adding and releasing with regressions should not be the
default mode of operation.

It should be
1. Mark every regression as blocking
2. Make an effort to fix the bugs you caused and help others to fix theirs
3. If some individual bug is too difficult to fix, make a concious decission
   to move that specific bugs blocking tag to the next release
4. If teh release gets delayed too much, its possible to release with the
   regressions, because "no release" can be worse


> otherwise nothing ever
> gets finished.

Lets look at the facts
we have 151 open/new bugs marked as regressions, 3 of them are less than
8 months old.
That means 2 things

1. we have hundreads of old regressions (some maybe even arent reported)
that are not getting fixed. Thats an issue and more attention should be
brought to them.

2. we have 3 regressions that are new, I do think we can and should
handle fixing new regressions.

and 3. we arent really blocking the release, the blocking tag is flexible
and very easy to change to the next release. But it gives things more vissibility

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Into a blind darkness they enter who follow after the Ignorance,
they as if into a greater darkness enter who devote themselves
to the Knowledge alone. -- Isha Upanishad

[-- 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:[~2024-04-04 11:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 22:57 Michael Niedermayer
2024-04-04  5:27 ` Jean-Baptiste Kempf
2024-04-04  7:12 ` Anton Khirnov
2024-04-04 11:47   ` Michael Niedermayer [this message]
2024-04-04 11:50     ` James Almer
2024-04-04 12:29       ` Michael Niedermayer
2024-04-04 12:51         ` James Almer
2024-04-04 16:39           ` Michael Niedermayer
2024-04-04 12:46       ` Michael Niedermayer

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=20240404114715.GV6420@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