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] [PATCH] Website release notes for 5.0
Date: Sat, 15 Jan 2022 15:24:00 +0100
Message-ID: <20220115142400.GT2829255@pb2> (raw)
In-Reply-To: <MtQCI7F--3-2@lynne.ee>


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

On Sat, Jan 15, 2022 at 01:48:40AM +0100, Lynne wrote:
> 14 Jan 2022, 20:39 by dev@lynne.ee:
> 
> > 14 Jan 2022, 20:32 by michael@niedermayer.cc:
> >
> >> On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
> >>
> >>> 14 Jan 2022, 18:48 by michael@niedermayer.cc:
> >>>
> >>> > On Tue, Jan 04, 2022 at 04:08:49PM +0100, Lynne wrote:
> >>> >
> >>> >> Since I couldn't find a codename preference, I went with "Desitter"
> >>> >>
> >>> >
> >>> > I just counted and i see 
> >>> > 2 for Desitter (the initial from the past and you)
> >>> > 3 for Lorentz  (the initial from the past, jb and reto )
> >>> >
> >>>
> >>> Changed the name locally to Lorentz.
> >>>
> >>
> >> ive just tagged the release and am uploading the tar.* files
> >> so you can push this
> >>
> >
> > 🎉 <https://emojipedia.org/party-popper/>
> > I've pinged j-b, since he wanted the announcement to wait
> > on something.
> >
> 
> Okay, the release will be officially out on 16:00 UTC+1 (CET) on Monday, the 17th,

The release was made, tagged and uploaded jannuary 14th its public since then
also the IRC topic has been updated with the release january the 14th

Isnt it better if the webpage is consistent and also points to the 14th ?


> so I'll push the update to the webpage then.
> Until then, go and test, or don't look back and hope a ninja 5.1 release won't be necessary :)

Testing should have been done before the release was tagged and the archieve
published. The branch was available for testing for quite a while too
Also I do test releases before i tag them but iam just one and doing pretty
much the same tests each time so theres systemic bias

I imagine we will have a 5.0.1 probably in a few weeks as more bugs are
found and fixed

Also, thanks for helping with the website update, i certainly appreciate
that you are helping here 

thx

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

I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates

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

  parent reply	other threads:[~2022-01-15 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 15:08 Lynne
2022-01-14 17:48 ` Michael Niedermayer
2022-01-14 19:02   ` Lynne
2022-01-14 19:32     ` Michael Niedermayer
2022-01-14 19:39       ` Lynne
     [not found]       ` <MtP5RG1--3-2@lynne.ee-MtP5UWd----2>
2022-01-15  0:48         ` Lynne
2022-01-15  4:08           ` Gyan Doshi
2022-01-15  5:01             ` Lynne
2022-01-15 12:14               ` James Almer
2022-01-15 14:24           ` Michael Niedermayer [this message]
2022-01-15 18:12             ` Lynne
     [not found]         ` <MtQCI7F--3-2@lynne.ee-MtQCMey----2>
2022-01-17 15:03           ` 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=20220115142400.GT2829255@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