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 7C37D44D52 for ; Sat, 21 Jan 2023 21:30:46 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id C138668BA5F; Sat, 21 Jan 2023 23:30:42 +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 458F868AC3F for ; Sat, 21 Jan 2023 23:30:36 +0200 (EET) Received: by mail-ed1-f49.google.com with SMTP id v30so10506971edb.9 for ; Sat, 21 Jan 2023 13:30:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:message-id:date:subject:to:from :from:to:cc:subject:date:message-id:reply-to; bh=HGV/DyD1hfqK+wvewfIPRDIbsTDaDdriqrengy82LMY=; b=i450spDcvClKDknKhMGu7WjW1C1Vm4oUSzZS86EV64U2tXrmpbj0Vux1CRCY1RS1hf hSR86kKEBKmW/y1C6aPBbXk0rO5lQKZ5g3n6SBTfTLWaF2nMEwxvjRejhpyZHlgzNXRg /E9NMtHKuIqh6anDb03kOmrOU1dyyxg2yPIXBI7b5uqrGhaYjQUU1H/dHyV7F7s77Uu0 1y/ardy/FXk7KwcLXTOHvD9+4mvC91wpIOEi4ZW+dbYqJQWN1ljeil5KMS1W997gdPP+ h/Qb5ULF0JGXbH/ZzK/WFZkyBI2Bgo5KM1ozs1zpEk+eXBzVZJwYqCOI/oSWIR9Q/402 46jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=HGV/DyD1hfqK+wvewfIPRDIbsTDaDdriqrengy82LMY=; b=K0AML7yoWy4x9P7+qxB3P7a17wqfSGU4W7OtwjvuhAjzrGuwqtoheQkzI+kR/2RAzi baXYVC1RhxgSa194UlFFtgtNUkkPGnjvalDPyasm+iI02CJMxhToDX3v1YwOwDPzuC0v /i6yEhhlwWqjTieBm8yqGSBjJtBEpVrpAHJvjhuQ0yvj2chvmhfI3WuBOEppjUpzjPXk /J1Cwa3P9/F9LAFAH0/XeVknvHfQxfxH4WCZ14JpCSEaq1sruPcgEloCC5K8wSLRmzbb ics9/ljRA7IlX01wdYswPAWIJUVETDSIkF3ByqoH/0mTkHdinl0EVDtmEJfCDA8yyyVE 2K3Q== X-Gm-Message-State: AFqh2kq8iBpJFgs6CVK8b/qe9QDGhMMtnKunQhqX81OXTnmTPn3pHWEa q9P/+HQjArJZLD8GIHwsUOQlZeQPz88= X-Google-Smtp-Source: AMrXdXv82IhPIPEOlMXUqZTzdkmhAdBxVd9zfLBN1A+eGuA2oRULZYhz4xTVKqgaJiDf/gAIiHevKA== X-Received: by 2002:a50:e610:0:b0:49e:c16:2c0f with SMTP id y16-20020a50e610000000b0049e0c162c0fmr18765957edm.1.1674336635286; Sat, 21 Jan 2023 13:30:35 -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 v19-20020a509553000000b0046cbcc86bdesm19499021eda.7.2023.01.21.13.30.34 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Jan 2023 13:30:34 -0800 (PST) From: Marvin Scholz To: FFmpeg development discussions and patches Date: Sat, 21 Jan 2023 22:30:33 +0100 X-Mailer: MailMate (1.14r5898) Message-ID: In-Reply-To: References: <20230116133840.512-1-jamrial@gmail.com> <167407008302.4503.12911207010634660934@lain.khirnov.net> <20230120020509.GX1949656@pb2> <167431989409.26119.3043585718968218@lain.khirnov.net> 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: On 21 Jan 2023, at 21:17, Hendrik Leppkes wrote: > On Sat, Jan 21, 2023 at 8:33 PM Marvin Scholz wrote: >>> >>> Alternatively, we could just not have an instability period at all. >>> >> >> Not having any instability period at all seems like a bad idea. >> > > Actually that sounds like the best idea. You would just have to > prepare the bump in a branch and all unstable changes ready to merge > in an instant. > Miss it? Tough. Having months long periods so people can get their > stuff sorted is way too long. Ideally it should be prepared ahead of > time and only a "soft instability" period of maybe two weeks reserved > for bug fixes (don't want to sit on issues for ever), rather then big > changes or new features. > How would it work? If I now make a branch with a breaking change, where would I put it and how would I get it merged together with the other breaking changes? Or do you mean that there should be a public devel branch where API/ABI breaking patches can be proposed for that will eventually be merged into master at a defined point in time together with major bump? > - Hendrik > _______________________________________________ > 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".