15 Jan 2022, 01:48 by d...@lynne.ee:
> 14 Jan 2022, 20:39 by d...@lynne.ee:
>
> Okay, the release will be officially out on 16:00 UTC+1 (CET) on Monday, the
> 17th,
> so I'll push the update to the webpage then.
>
Website updated, so I think that makes the release officially announced.
_
15 Jan 2022, 15:24 by mich...@niedermayer.cc:
> On Sat, Jan 15, 2022 at 01:48:40AM +0100, Lynne wrote:
>
>> 14 Jan 2022, 20:39 by d...@lynne.ee:
>>
>> > 14 Jan 2022, 20:32 by mich...@niedermayer.cc:
>> >
>> >> On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
>> >>
>> >>> 14 Jan 2022, 18:48 b
On Sat, Jan 15, 2022 at 01:48:40AM +0100, Lynne wrote:
> 14 Jan 2022, 20:39 by d...@lynne.ee:
>
> > 14 Jan 2022, 20:32 by mich...@niedermayer.cc:
> >
> >> On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
> >>
> >>> 14 Jan 2022, 18:48 by mich...@niedermayer.cc:
> >>>
> >>> > On Tue, Jan 04, 2
On 1/15/2022 2:01 AM, Lynne wrote:
15 Jan 2022, 05:08 by ffm...@gyani.pro:
On 2022-01-15 06:18 am, Lynne wrote:
14 Jan 2022, 20:39 by d...@lynne.ee:
14 Jan 2022, 20:32 by mich...@niedermayer.cc:
On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
14 Jan 2022, 18:48 by mich...@nie
15 Jan 2022, 05:08 by ffm...@gyani.pro:
>
>
> On 2022-01-15 06:18 am, Lynne wrote:
>
>> 14 Jan 2022, 20:39 by d...@lynne.ee:
>>
>>> 14 Jan 2022, 20:32 by mich...@niedermayer.cc:
>>>
On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
> 14 Jan 2022, 18:48 by mich...@niedermayer.cc:
On 2022-01-15 06:18 am, Lynne wrote:
14 Jan 2022, 20:39 by d...@lynne.ee:
14 Jan 2022, 20:32 by mich...@niedermayer.cc:
On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
14 Jan 2022, 18:48 by mich...@niedermayer.cc:
On Tue, Jan 04, 2022 at 04:08:49PM +0100, Lynne wrote:
Since I c
14 Jan 2022, 20:39 by d...@lynne.ee:
> 14 Jan 2022, 20:32 by mich...@niedermayer.cc:
>
>> On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
>>
>>> 14 Jan 2022, 18:48 by mich...@niedermayer.cc:
>>>
>>> > On Tue, Jan 04, 2022 at 04:08:49PM +0100, Lynne wrote:
>>> >
>>> >> Since I couldn't find
14 Jan 2022, 20:32 by mich...@niedermayer.cc:
> On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
>
>> 14 Jan 2022, 18:48 by mich...@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"
>>
On Fri, Jan 14, 2022 at 08:02:35PM +0100, Lynne wrote:
> 14 Jan 2022, 18:48 by mich...@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
14 Jan 2022, 18:48 by mich...@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 t
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 )
[...]
--
Michael GnuPG fingerp
Since I couldn't find a codename preference, I went with "Desitter"
(even though the correct spelling is "De Sitter"). There's a joke in
here that if we mess up and need a 5.1 release quickly, we could
codename it "anti-Desitter" :)
The release notes go as follows:
FFmpeg 5.0 "Desitter", a new
12 matches
Mail list logo
