From: Zane van Iperen <zane@zanevaniperen.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] 5.0 release Date: Mon, 03 Jan 2022 00:50:54 +1000 Message-ID: <35404072.zGk2CCufKt@morningstar> (raw) In-Reply-To: <c685c78c-b612-9145-65e5-1f50e5f9d2bd@gmail.com> On Monday, 3 January 2022 12:29:02 AM AEST James Almer wrote: > > 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? > > It's a good idea, but we need to be strict about it. As in, we need to > state that the moment the branch is made it's a definite feature freeze, > and only fixes, documentation changes and similar may be cherry-picked > into it (meaning nothing that usually comes with a version bump, even if > micro), much like we do for a point release, even if the initial release > was not tagged yet. > I completely agree, this is a *very* good idea. If people treat it like an existing release branch, i.e. only bugfixes, etc., then it would save this from happening again. Also means there wouldn't need to be a "don't add big things" announcement _somewhere_ on the ML. > Reverting something in the release branch is already going to be dirty > no matter what, because we do a minor bump to ensure the release has its > own soname. Right now that'd mean 5.0 will be lavf 59.13, while lacking > a demuxer available in lavf 59.12 Depends on what you mean by "lacking a demuxer"... One (hacky) option would be to replace it with a stub implementation that always fails. Or we could just branch off at 7cee3b3718 and cherry-pick anything we need back. There's only like four commits that need it (so far): 2f6360ff21, 9cfc7a2440, c417616762, and d6b2357edd. _______________________________________________ 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-02 14:51 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 2022-01-02 14:29 ` James Almer 2022-01-02 14:50 ` Zane van Iperen [this message] 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=35404072.zGk2CCufKt@morningstar \ --to=zane@zanevaniperen.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