From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 92CD148054 for ; Thu, 9 Nov 2023 09:46:36 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 24E1368CB3B; Thu, 9 Nov 2023 11:46:33 +0200 (EET) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0BA3268C74F for ; Thu, 9 Nov 2023 11:46:27 +0200 (EET) Received: by mail-ed1-f49.google.com with SMTP id 4fb4d7f45d1cf-5435336ab0bso1029151a12.1 for ; Thu, 09 Nov 2023 01:46:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699523186; x=1700127986; darn=ffmpeg.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:to:from:from:to:cc:subject:date:message-id :reply-to; bh=nD/YquAlNOZ8zUaKemm/zvLF1/BHMFD3QzDwrz9EeCg=; b=AEB+TKWBvGWsTxbMf8iDcv+dL3Eq+VtjQfgUzu61u+6PKG7TqaDqKYDbaH82OJhp0u zSjdSu5RScx+9it8516TWrKz6bLtI8/aabF6PMYCurDXVQE5VldEMO8aNYZ60cYYmlbR BcAHXWeC9W+jGOf8CDlhpjCHkmJJBplNIyA28rVDiUAZCwhkYnxchOQXH6tow4TRlr0K Qso2mFamNR+Jft7EVcTEBaCM3SFclujxapkczKomBEqfDNRVdQ/eFgD14Bmfcecx+R3N iUjU220ftn6AQeRqz7wlMbxdyYdKeNPO5C1lcs2Fn3vUXFqTLtmhPvv4UUu9JZZ/hA67 4YSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699523186; x=1700127986; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=nD/YquAlNOZ8zUaKemm/zvLF1/BHMFD3QzDwrz9EeCg=; b=Mit7w8lZCXu2zOf0t/e65/fS4/b99LhJkFNZ9mWXkudoO7VwQPCzqPssEI1AHe6xpI ZYcg5Wn3WnsBRWPrc+ak2xRJzGkw+nKPl6TvN6XpX+VF+IFx/SUoE+TsYDJ5WI+ALXP1 hQtuFElMt4+ZEGzNRLa2gMsdmbhvqLja8WLu5RhggyjNmHPL9FRDVBzb92vJjQ5tUjDl P4nxaxBS930p260UALE34jjYvZRexZ83iIyoYX69MmMaUipoiKdc5ae20VP6TBN8+P8+ Y5IakvS70ZEm+OBCl1JdtjrV0Cun9WHr45katxasFOXStrr7tFkSVW3DsyRvKOuIY7l0 lbdg== X-Gm-Message-State: AOJu0YyDUFgptV3YQCCqJTpt9ifbBPgxghro1aOLbQK1OBAghXJ7/WPc exd7ux/FCpcGz8goyTt5hyL7nA3sYz4XOQ== X-Google-Smtp-Source: AGHT+IEpf2sgrVjcWl662JvOpq4nWBwDSQeqhu/+Y42FFKzHJmYEHabgYZ6rGimcQAbupHY4fj5hHQ== X-Received: by 2002:a17:907:7ea9:b0:9c6:10d4:d09f with SMTP id qb41-20020a1709077ea900b009c610d4d09fmr4297550ejc.63.1699523185924; Thu, 09 Nov 2023 01:46:25 -0800 (PST) Received: from [192.168.1.104] (84-112-104-25.cable.dynamic.surfer.at. [84.112.104.25]) by smtp.gmail.com with ESMTPSA id lh18-20020a170906f8d200b009dd4b2d412fsm2305358ejb.36.2023.11.09.01.46.24 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2023 01:46:25 -0800 (PST) From: epirat07@gmail.com To: FFmpeg development discussions and patches Date: Thu, 09 Nov 2023 10:46:24 +0100 X-Mailer: MailMate (1.14r5937) Message-ID: In-Reply-To: References: <20231028164945.GC3543730@pb2> <20231029045125.GI3543730@pb2> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [RFC] Release 6.1 X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 9 Nov 2023, at 9:20, Lynne wrote: > Nov 7, 2023, 08:36 by dev@lynne.ee: > >> Oct 29, 2023, 06:57 by dev@lynne.ee: >> >>> Oct 29, 2023, 05:51 by michael@niedermayer.cc: >>> >>>> On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote: >>>> >>>>> Oct 28, 2023, 18:49 by michael@niedermayer.cc: >>>>> >>>>>> On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote: >>>>>> >>>>>>> It's been a while since we've had a release, and we've had >>>>>>> a lot of new features in. >>>>>>> We did say we would make releases more often, and I think >>>>>>> it's about time we have a new release. >>>>>>> >>>>>>> Anything anyone wants to have merged or should we branch >>>>>>> off 6.1 in a few days? >>>>>>> >>>>>> >>>>>> Whats the status of this ? >>>>>> I can branch 6.1 anytime >>>>>> >>>>>> 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" >>>>>> >>>>>> but now i see on IRC >>>>>> make a damn release already >>>>>> j-b: drop MiNi from release maintership and nominate Lynne >>>>>> I pledge to bring back /slap IRC messages to those who fail to push the patches they want for release! >>>>>> durandal_1707: good point, we should look at doing another 5.1.x release and a 6.0.x release. >>>>>> >>>>>> noone mentioned 5.1.x and 6.0.x to me before >>>>>> >>>>>> anyway, ill try to make releases from all maintained branches, >>>>>> >>>>>> and will branch 6.1 as soon as Lynne or others say everything is ready. >>>>>> >>>>>> thx >>>>>> >>>>> >>>>> It's never too late to make a release. If we do a release now, nothing's stopping >>>>> us from doing a 7.0 and getting back on track with releases every two months or so, >>>>> like the plan was. >>>>> >>>>> 7.0 is likely to be a pretty big release, with YUVJ removal, (xHE) AAC+fixes, D3D12 hwdec, >>>>> Vulkan encode and Vulkan AV1, and VVC, and IAMF, and MLP work, so it's a good idea to >>>>> have a release before all this lands. >>>>> >>>>> I think the tree is in a pretty good state ATM, you should go ahead and branch if you're >>>>> comfortable with it as well. >>>>> >>>> >>>> branch made >>>> >>> >>> Thanks. I'll get a blog post ready for the transform work, as kierank wanted to post something, >>> and if users can know to who to point fingers to in case it degrades performance on RPI1 devices. >>> >>> >>>>> Let's aim for a release by Sunday next week. That should give everyone enough time to >>>>> backport fixes they want in. >>>>> >>>> >>>> I would aim for 1-3 weeks (when code and developers are ready) >>>> dont want to aim for a specific day, better pick a day when everything is fine >>>> not too many distractions, ... >>>> >>>> Or is there something that favors us to be before a specific date ? >>>> >>> >>> Not really a reason, Sunday is just an optimistic date to aim for. >>> If there are no big fixes to backport to the branch, I think we can target it. >>> >> >> The nlmeans_vulkan patch I just sent is the last patch I'd like to have in 6.1. >> Does anyone else have any patches they would like in 6.1? If 6.1 will be cut from master, my tpad fix I sent yesterday should probably be applied first to prevent having a release with broken tpad. >> > > Pushed the 2 patches. > > Michael, do you think you can tag the release late tonight? > No one has said anything yet. > I'll write release notes for the website by then as well. > _______________________________________________ > 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".