From: Niklas Haas <ffmpeg@haasn.xyz> To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] 7.0 blocking issues Date: Mon, 25 Mar 2024 14:50:19 +0100 Message-ID: <20240325145019.GB17553@haasn.xyz> (raw) In-Reply-To: <2366ae95-3ea6-4c61-addc-b4a4667febb0@betaapp.fastmail.com> On Mon, 25 Mar 2024 07:20:56 +0100 "Jean-Baptiste Kempf" <jb@videolan.org> wrote: > Hello, > > On Mon, 25 Mar 2024, at 01:03, Michael Niedermayer wrote: > > Should i wait till all issues marked as blocking 7.0 on trac are fixed > > before branching ? > > I think you should branch now. > And get things fixed in the 7.0 branch. +1 This is a big change and some breakage is inevitable. Most bugs will probably only be found once the software is released and deployed. When a big milestone gets bogged down by months (if not years) of "blocking bugs", my understanding is that it will simply never get released, and users might as well resort to using git master / nightly builds at that point. (Any possible allusion to *other* big open source software projects is purely coincidental) > > -- > Jean-Baptiste Kempf - President > +33 672 704 734 > https://jbkempf.com/ > _______________________________________________ > 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:[~2024-03-25 13:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 0:03 Michael Niedermayer 2024-03-25 0:35 ` James Almer 2024-03-25 2:30 ` Michael Niedermayer 2024-03-25 6:20 ` Jean-Baptiste Kempf 2024-03-25 13:50 ` Niklas Haas [this message] 2024-03-25 20:20 ` Lynne 2024-03-25 21:10 ` Michael Niedermayer 2024-03-25 21:18 ` Kieran Kunhya 2024-03-25 21:57 ` Michael Niedermayer 2024-03-25 21:29 ` James Almer
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=20240325145019.GB17553@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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