Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] 5.0 release
Date: Sun, 02 Jan 2022 15:12:37 +0100
Message-ID: <164113275711.2375.2561092812450139105@lain.red.khirnov.net> (raw)
In-Reply-To: <20211231194024.GJ2829255@pb2>

Quoting Michael Niedermayer (2021-12-31 20:40:24)
> On Fri, Dec 31, 2021 at 10:45:46PM +0530, Gyan Doshi wrote:
> > 
> > 
> > On 2021-12-31 10:22 pm, Michael Niedermayer wrote:
> > > On Tue, Dec 28, 2021 at 12:55:14AM +0100, Michael Niedermayer wrote:
> > > > On Wed, Dec 22, 2021 at 05:44:42PM +0100, Jean-Baptiste Kempf wrote:
> > > > > On Wed, 22 Dec 2021, at 15:05, James Almer wrote:
> > > > > > Is the December target to get into the feature freeze schedule from
> > > > > > distros?
> > > > > No, it was set by me, in order to get the distro freezes from January.
> > > > > 
> > > > > We can miss the target a bit this year, and then make it better for 2022.
> > > > as you seem to know the distro freeze shedules
> > > > can you clarify "a bit" ?
> > > > 
> > > > iam asking just in case the channel patch doesnt make it before
> > > > so i know when its time to stop waiting for it
> > > ok
> > > when do people want me to make the branch ?
> > > any preferrances ?
> > > should i do it now or continue waiting?
> > > 
> > > I saw on IRC some sugestions to make it at a past commit to keep some
> > > code out
> > 
> > It would be nice to have a public date set a few days into the future.
> 
> yes, i intended to do that, unless people wanted a ASAP/NOW branch
> 
> i guess 3rd january seems like a good choice
> 1st and 2nd as being close to newyear probably would not be ideal so
> 3rd seems the soonest good date
> but we can push this out more if people want? or also do it earlier
> of course that assumes nothing unexpected happens
> (and something unexpected always happens...)

There were some disagreements on IRC a few days ago about what should
and should not go into the release because of insufficient fuzzing and
the danger of introducing security issues.

To avoid conflicts around this in the future, I'd suggest (for future
releases) to create the release branch a significant time (e.g. a month)
before doing the actual release.

Opinions?

-- 
Anton Khirnov
_______________________________________________
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-02 14:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211125171932.GC2829255@pb2>
     [not found] ` <20211213152557.GL2829255@pb2>
     [not found]   ` <CABcAi1jFnkGd-dyLy_iOHhKEVUz=OPYXp23X326_6okM+zW8Aw@mail.gmail.com>
     [not found]     ` <20211214161924.GM2829255@pb2>
     [not found]       ` <CABcAi1h45bkw4rmYJYEJrEaqOybbFvqXZFAAJ6F5=Mo4+BPHVg@mail.gmail.com>
2021-12-15 14:52         ` Michael Niedermayer
2021-12-15 15:08           ` Diederick C. Niehorster
2021-12-15 15:15             ` Michael Niedermayer
     [not found]   ` <3238136b-1f43-49ae-b2d6-ce98b98e24f0@www.fastmail.com>
2021-12-22 14:03     ` Michael Niedermayer
2021-12-22 14:05       ` James Almer
2021-12-22 16:44         ` Jean-Baptiste Kempf
2021-12-27 23:55           ` Michael Niedermayer
2021-12-31 16:52             ` Michael Niedermayer
2021-12-31 17:15               ` Gyan Doshi
2021-12-31 19:40                 ` Michael Niedermayer
2022-01-02 14:12                   ` Anton Khirnov [this message]
2022-01-02 14:29                     ` James Almer
2022-01-02 14:50                       ` Zane van Iperen
2022-01-02 15:09                         ` James Almer
2022-01-02 15:52                           ` Zane van Iperen
2022-01-02 16:28                             ` Lynne
2022-01-02 17:11                               ` Michael Niedermayer
2022-01-02 18:12                                 ` Lynne
2022-01-02 22:29                                   ` Michael Niedermayer
2022-01-02 22:32                                     ` Michael Niedermayer
2022-01-03  5:31                   ` Jean-Baptiste Kempf
2022-01-03 16:14                     ` Michael Niedermayer
2022-01-03 17:17                       ` Hendrik Leppkes
2022-01-03 17:19                         ` Hendrik Leppkes
2022-01-03 18:04                         ` Paul B Mahol
2022-01-03 18:58                           ` Michael Niedermayer
2022-01-03 19:25                             ` Paul B Mahol
2022-01-03 20:14                               ` Michael Niedermayer
2022-01-03 20:29                                 ` Paul B Mahol
2022-01-03 20:36                                   ` Michael Niedermayer
2022-01-03 19:23                       ` Michael Niedermayer
2022-01-04  2:11                     ` Soft Works
2021-12-31 19:08               ` Lynne

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=164113275711.2375.2561092812450139105@lain.red.khirnov.net \
    --to=anton@khirnov.net \
    --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