From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] Website release notes for 5.0 Date: Sat, 15 Jan 2022 09:14:42 -0300 Message-ID: <94f02315-8eab-8ec2-4a26-712135ad1de4@gmail.com> (raw) In-Reply-To: <MtR6CMv--3-2@lynne.ee> On 1/15/2022 2:01 AM, Lynne wrote: > 15 Jan 2022, 05:08 by ffmpeg@gyani.pro: > >> >> >> On 2022-01-15 06:18 am, 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, >>> 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 :) >>> >> >> Michael has tagged, so it's already 'out' , no? >> > > No. It's just a freeze, and if something really bad is found, > we can still redo it. The 5.0 release is tagged, that's not going to change. You can however sneakily tag a 5.0.1 point release if you think 5.0 has severe problems and then upload the tarballs for that version instead as the first available one. > You generally shouldn't do releases on a Friday night, or > weekends, for obvious reasons. > _______________________________________________ > 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". _______________________________________________ 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".
next prev parent reply other threads:[~2022-01-15 12:14 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 [this message] 2022-01-15 14:24 ` Michael Niedermayer 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=94f02315-8eab-8ec2-4a26-712135ad1de4@gmail.com \ --to=jamrial@gmail.com \ --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