From: "Jean-Baptiste Kempf" <jb@videolan.org> To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Release 6.1 Date: Sun, 29 Oct 2023 17:42:12 +0100 Message-ID: <f44f890f-5f5f-4a0a-a00c-d6a447c31512@betaapp.fastmail.com> (raw) In-Reply-To: <20231028164945.GC3543730@pb2> Hello, On Sat, 28 Oct 2023, at 18:49, Michael Niedermayer wrote: > noone mentioned 5.1.x and 6.0.x to me before Our last releases from our two major bracnhes, are a 5.1.3 (which is a LTS branch) and a 6.0.0. Both of those have not had backports and releases of all the security issues, nor on the major regressions found (if any). Also, if they had some commits for security reasons, we should have a release at least every 90 days (3 months), because this is the standard for the security issues reporting (after that time, the security community makes them public). And seeing the number of fuzzing fixes, this is likely important. So, yes, I think having a 5.1.4 and 6.0.1 with the security fixes is of the utmost importance. > It was just that jb told me > "6.1 opportunity is gone. > We're too late on the schedule, and noone had time to work on it, so > it is wiser to target 7.0 in January" Yes, we said we would make a new major version for January (which will slip in February, as usual :D). So, doing a 6.1.0 now, while 7.0 is not far away, might be a lot of work and it might not worth it. Notably since at the time of 7.0, there might be not enough new things to cut a release. So I'm not against a release for 6.1 at all, but I believe focusing on minor releases for security and on 7.0 with the next major deprecations is more important. If we can do all of those, and keep more or less the timing for 7.0, please be my guest for 6.1. -- Jean-Baptiste Kempf - President +33 672 704 734 _______________________________________________ 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:[~2023-10-29 16:42 UTC|newest] Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-06 16:04 Lynne 2023-07-06 16:19 ` Jean-Baptiste Kempf [not found] ` <4e164164-f730-4b5e-9edc-1a37b10684e2@betaapp.fastmail.com-NZg-97N----9> 2023-07-07 6:40 ` Lynne 2023-07-07 6:53 ` Ingo Oppermann 2023-07-07 7:36 ` Steven Liu 2023-09-26 13:37 ` Leo Izen 2023-07-07 15:06 ` Michael Niedermayer 2023-07-07 15:33 ` Lynne 2023-07-07 22:51 ` Michael Niedermayer 2023-07-09 10:14 ` Anton Khirnov 2023-09-22 9:27 ` Michael Niedermayer 2023-09-22 9:32 ` Paul B Mahol 2023-09-22 14:49 ` Michael Niedermayer 2023-09-22 15:27 ` Paul B Mahol 2023-09-26 8:47 ` Jean-Baptiste Kempf 2023-09-22 10:04 ` Nicolas George 2023-09-22 11:42 ` Paul B Mahol 2023-09-26 9:13 ` Anton Khirnov 2023-09-26 15:09 ` Michael Niedermayer 2023-09-26 15:14 ` Kieran Kunhya via ffmpeg-devel 2023-09-26 15:30 ` Anton Khirnov 2023-09-26 16:27 ` Derek Buitenhuis 2023-09-26 17:24 ` Michael Niedermayer 2023-09-26 17:16 ` Michael Niedermayer 2023-09-26 17:25 ` James Almer 2023-09-26 18:03 ` Nicolas George 2023-09-26 18:14 ` Anton Khirnov 2023-09-26 18:24 ` Nicolas George 2023-09-26 18:27 ` Vittorio Giovara 2023-09-26 18:28 ` Nicolas George [not found] ` <F3D5B4BB-AE60-401F-800E-6246B9F359A4@cosmin.at> 2023-09-26 22:50 ` [FFmpeg-devel] SDR choices Cosmin Stejerean via ffmpeg-devel 2023-10-03 19:22 ` [FFmpeg-devel] [RFC] Release 6.1 Michael Niedermayer 2023-10-04 15:19 ` Anton Khirnov 2023-10-04 16:54 ` Lynne 2023-10-04 17:53 ` Michael Niedermayer 2023-09-26 21:20 ` Ronald S. Bultje 2023-09-27 13:53 ` Tomas Härdin 2023-09-27 20:18 ` Michael Niedermayer 2023-09-27 20:27 ` Nicolas George 2023-09-28 8:48 ` Ronald S. Bultje 2023-09-28 14:45 ` Rémi Denis-Courmont 2023-09-28 15:33 ` Nicolas George 2023-09-28 15:58 ` Rémi Denis-Courmont 2023-09-28 16:13 ` Nicolas George 2023-09-28 16:34 ` Rémi Denis-Courmont 2023-09-28 16:42 ` Nicolas George 2023-09-28 14:32 ` Rémi Denis-Courmont 2023-09-28 15:28 ` Nicolas George 2023-09-28 16:22 ` Rémi Denis-Courmont 2023-09-28 16:32 ` Nicolas George 2023-09-28 16:35 ` Paul B Mahol 2023-09-28 16:38 ` Rémi Denis-Courmont 2023-09-28 16:41 ` Nicolas George 2023-09-28 16:42 ` Rémi Denis-Courmont 2023-09-28 16:43 ` Nicolas George 2023-09-28 17:27 ` Rémi Denis-Courmont 2023-07-08 1:46 ` Neal Gompa 2023-07-09 10:13 ` Anton Khirnov 2023-10-09 3:37 ` Lynne 2023-10-09 17:41 ` Michael Niedermayer 2023-10-10 15:19 ` Neal Gompa 2023-10-28 16:49 ` Michael Niedermayer 2023-10-28 16:56 ` James Almer 2023-10-28 19:23 ` Lynne 2023-10-29 4:51 ` Michael Niedermayer 2023-10-29 5:57 ` Lynne 2023-11-07 7:36 ` Lynne 2023-11-07 16:47 ` Tristan Matthews 2023-11-08 1:26 ` Steven Liu 2023-11-08 1:29 ` Steven Liu [not found] ` <NichQkq--3-9@lynne.ee-NichTw8----9> 2023-11-09 8:20 ` Lynne 2023-11-09 9:46 ` epirat07 2023-11-09 9:48 ` Gyan Doshi 2023-11-10 1:47 ` Michael Niedermayer 2023-10-29 9:30 ` Nicolas George 2023-10-29 13:51 ` Jean-Baptiste Kempf 2023-10-29 14:17 ` Nicolas George 2023-10-29 16:27 ` Jean-Baptiste Kempf 2023-10-29 16:40 ` Nicolas George 2023-10-29 16:43 ` Jean-Baptiste Kempf 2023-10-29 16:45 ` Nicolas George 2023-10-29 15:10 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 16:25 ` Jean-Baptiste Kempf 2023-10-29 17:20 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 17:56 ` Jean-Baptiste Kempf 2023-10-29 18:12 ` Nicolas George 2023-10-29 18:22 ` Jean-Baptiste Kempf 2023-10-29 18:31 ` Nicolas George 2023-10-29 19:11 ` Jean-Baptiste Kempf 2023-10-29 19:19 ` Nicolas George 2023-10-29 18:47 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 18:46 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 19:27 ` Jean-Baptiste Kempf 2023-11-01 17:53 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 16:42 ` Jean-Baptiste Kempf [this message] 2023-10-29 16:49 ` James Almer 2023-10-29 17:01 ` Jean-Baptiste Kempf
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=f44f890f-5f5f-4a0a-a00c-d6a447c31512@betaapp.fastmail.com \ --to=jb@videolan.org \ --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