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 14772436C6 for ; Fri, 20 Jan 2023 15:08:10 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E648F68BCC5; Fri, 20 Jan 2023 17:08:06 +0200 (EET) Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C8B6468A4CA for ; Fri, 20 Jan 2023 17:07:59 +0200 (EET) Received: from [10.10.150.87] (1346516434.ip.84grams.net [134.65.164.34]) by mail.frobbit.se (Postfix) with ESMTPSA id B7113248E3 for ; Fri, 20 Jan 2023 16:07:57 +0100 (CET) Message-ID: From: Tomas =?ISO-8859-1?Q?H=E4rdin?= To: FFmpeg development discussions and patches Date: Fri, 20 Jan 2023 16:07:57 +0100 In-Reply-To: References: <20230116133840.512-1-jamrial@gmail.com> <167407008302.4503.12911207010634660934@lain.khirnov.net> User-Agent: Evolution 3.38.3-1+deb11u1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 00/26] Major library version bump 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: ons 2023-01-18 klockan 18:23 -0300 skrev James Almer: > On 1/18/2023 4:28 PM, Anton Khirnov wrote: > > Quoting James Almer (2023-01-16 14:38:14) > > > It's been a while since the last bump, so it's time to do some > > > cleaning and > > > remove deprecated APIs. This will also give us an "Open ABI > > > season" in which we > > > can do breaking changes (like changing public struct offsets, > > > public enum > > > values, adding fields to structs that have their size tied to the > > > ABI, etc) for > > > a few weeks. > > > > Last time this open season lasted something like half a year and > > only > > ended when I arbitrarily said it did. > > > > So I'd suggest to decide right now how long will the instability > > period > > last (6 weeks should be enough for everybody) and write the end > > date at > > the top of doc/APIchanges. > > > > Another thing I'm not entirely happy about is versioning during the > > bump > > and instability. While the remove-then-bump approach does make > > bisection > > easier, it also creates commits that lie about their ABI version. > > Does it really matter? All the patches will be pushed at the same > time, > meaning one git fetch will give you a stable state pre bump and the > next > will be right after it. > I think it's a bit farfetched to expect someone to pick a random > commit > in the middle of the bump and try to use the resulting compiled > libraries with some program that was linked to some earlier version > libraries. This is easily fixed by having a feature branch for the bumps and merging it with --no-ff. git bisect is clever enough to skip past such things /Tomas _______________________________________________ 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".