From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) by sourceware.org (Postfix) with ESMTPS id AE5C53858416 for ; Wed, 12 Jan 2022 05:00:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AE5C53858416 Received: by mail-wm1-x330.google.com with SMTP id p18so721953wmg.4 for ; Tue, 11 Jan 2022 21:00:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ctbBWtosQ8HU2hjpqv2WeyrTPNlNHXOMrUiGDfzZ5Js=; b=K3cSTkTgNk4sZ11LjOKwbdpi7FivEO9UuthXEA715imaqBeqoEBY9skf1UT8HHTYPp Pv+/XkAg4D15Cyk2oWMWavis+c0gG/3GmY5pVhIV6PhHmWJoEzLT2fhlrqzcYben2o+z 3J0vGT9M3Qy9SGmShyoQwrD1EcoYXGXG4VelqedIswWioP+q+q+Ar0TiQkDSpKlZL6Xr +OqFyk6POMQ6BDqx3KA0ABPp0mTKxYdQeVe2qutTy5hqyG+8cqL1vfV+gOpPL513Nv57 PB+IyWO01wAm5kEB9apwv7IgAeWeJLZ6Dt/QlFRdbsDG8/cqp11yloeAFhEmiZB02mGK jyzQ== X-Gm-Message-State: AOAM532bS9TCBsP3zg/JDZmtI1LBoSyjm+EoH+8MrMiRpd6NLOvpTBI+ CInp70O215i60WSnDehYERXwROTJzrt2 X-Google-Smtp-Source: ABdhPJxTxZr2Qq2QceGsEhZERGwnCCza+JH0pAIuvQBExxtk3DrILa0Ssv0WSpgSx8w1X09K5cRnvw== X-Received: by 2002:a1c:19c1:: with SMTP id 184mr4246501wmz.61.1641963600691; Tue, 11 Jan 2022 21:00:00 -0800 (PST) Received: from takamaka.home ([2a01:cb22:1d5:1100:9f61:c476:272f:db95]) by smtp.gmail.com with ESMTPSA id a8sm6522709wrx.57.2022.01.11.20.59.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 21:00:00 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id B58B3A4A59; Wed, 12 Jan 2022 08:59:57 +0400 (+04) Date: Wed, 12 Jan 2022 08:59:57 +0400 From: Joel Brobecker To: gdb@sourceware.org Cc: Joel Brobecker Subject: Re: gdb branch policy in non-gdb code Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2022 05:00:03 -0000 > the gdb docs are little unclear: > https://sourceware.org/gdb/ about wiki/Internals%20Releasing-GDB > > it focuses on the gdb/ subdir. that makes sense -- the gdb branch is meant > for releasing gdb, and most bugfixes will be in that directory. > > but what about commits outside of gdb/ ? does the gdb branch maintainer > have to approve each one ? like something in bfd/ or libctf/ or sim/. > or is it good enough that it's already been approved & merged into master, > and the flow is more interested folks post a [committed] notification to > the list when they cherry-pick back ? This document gives guidelines in the decision process, but indeed doesn't talk about responsibilities. My position as the current manager of GDB releases is that Global Maintainers have the ability to approve that a patch be backported to a release branch. The idea behind it is that those Global Maintainers often have a better understanding of the ins and outs of a given patch and therefore of its potential impact. I think we can extend this to the Responsible Maintainers such as yourself as well for the patches that fall within their area of responsibility. Parallel to this, I am always happy to provide feedback on patches people would like me to evaluate. One important note is a reminder that patches backported to the .2 must have a PR number attached to them, with the target milestone set to the release in question. This is critical for the issue to list as being fixed in the .2 release. -- Joel